blob: 57da165fe43f9bc13da89f68248a1b81ae3a4a1a (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] database servers
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20database%20servers&In-Reply-To=%3C4D7A0C64.9090901%40roadrunner.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="003229.html">
<LINK REL="Next" HREF="003225.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] database servers</H1>
<B>Frank Griffin</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20database%20servers&In-Reply-To=%3C4D7A0C64.9090901%40roadrunner.com%3E"
TITLE="[Mageia-dev] database servers">ftg at roadrunner.com
</A><BR>
<I>Fri Mar 11 12:49:56 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="003229.html">[Mageia-dev] database servers
</A></li>
<LI>Next message: <A HREF="003225.html">[Mageia-dev] [RPM] cauldron core/release wine-gecko-1.1.0-2.mga1
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3235">[ date ]</a>
<a href="thread.html#3235">[ thread ]</a>
<a href="subject.html#3235">[ subject ]</a>
<a href="author.html#3235">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Oliver Burger wrote:
><i> Normally this is working nicely, but if you are using extensions to postgres
</I>><i> like postgis and so on (which may or may not be packaged and thus be selve
</I>><i> compiled), it can be a pain in the ass.
</I>><i>
</I>
"can be" --> "usually is".
I don't actually use postgre, but I have historically installed it to
have it available as an option. Every time the packages update, there
are conflicts that prevent seamless installation. IIRC this is due to
the desire to keep old versions around, Unfortunately, the new and old
packages usually have conflicts that prevent them being installed
side-by-side. I'm not sure if the expectation is that users will delay
the install of the new until they've dumped their databases using the
old, and then manually uninstall the old, but this breaks seamless updates.
If multiple versions are needed, please eliminate the conflicts between
the packages.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="003229.html">[Mageia-dev] database servers
</A></li>
<LI>Next message: <A HREF="003225.html">[Mageia-dev] [RPM] cauldron core/release wine-gecko-1.1.0-2.mga1
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3235">[ date ]</a>
<a href="thread.html#3235">[ thread ]</a>
<a href="subject.html#3235">[ subject ]</a>
<a href="author.html#3235">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|