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
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] ksnapshot conflicts with kdegraphics4-devel
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20ksnapshot%20conflicts%20with%20kdegraphics4-devel&In-Reply-To=%3C1309949724.6644.YahooMailNeo%40web161713.mail.bf1.yahoo.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="006392.html">
<LINK REL="Next" HREF="006378.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] ksnapshot conflicts with kdegraphics4-devel</H1>
<B>Radu-Cristian FOTESCU</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20ksnapshot%20conflicts%20with%20kdegraphics4-devel&In-Reply-To=%3C1309949724.6644.YahooMailNeo%40web161713.mail.bf1.yahoo.com%3E"
TITLE="[Mageia-dev] ksnapshot conflicts with kdegraphics4-devel">beranger5ca at yahoo.ca
</A><BR>
<I>Wed Jul 6 12:55:24 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="006392.html">[Mageia-dev] ksnapshot conflicts with kdegraphics4-devel
</A></li>
<LI>Next message: <A HREF="006378.html">[Mageia-dev] [RPM] cauldron core/release logrotate-3.8.0-1.mga2
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6393">[ date ]</a>
<a href="thread.html#6393">[ thread ]</a>
<a href="subject.html#6393">[ subject ]</a>
<a href="author.html#6393">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>
>><i> obsoletes are not the correct place for solve such problems.
</I>><i> ksnapshot don't have any obsoletes but a conflict (which is probably
</I>
><i> indeed too much but was not expected to add any problem i
</I>
Sorry to bother you, but since this is both about an upgrade and a change of package names (albeit via a fragmentation/split), why isn't "Obsoletes" a better choice?
If I am not very wrong, technically "Conflicts" will cause the install/upgrade to fail and therefore forbids an installation/upgrade. Which is both annoying and it requires a multiple-step action from the end-user's part. In contrast, "Obsoletes" forces an upgrade to the new packages names, automatically removing the old packages.
While in principle "Obsoletes" doesn't prevent the end-user from reinstalling the old package(s), this is not desired anyway. I mean, it's not like "kdesomething-4.6.4" and "kdesomesplitpackage-4.6.90" would coexist on the same machine -- it's either you upgraded from KDE 4.6.4 to 4.6.90, or you didn't.
So I suppose you say "Obsoletes" is not the right thing to do _as a principle_ (as a principle, GOTO is considered harmful too), but why is it unsuitable for this very case of an evolving (cauldron) repository in a situation of a kinky upgrade?
Of course, I am still waiting for a mentor, so I might be very, very wrong in my understanding of "Conflicts vs Obsoletes". What I believe I know is that "Obsoletes" makes things transparent for the end-user, whereas "Conflicts" looks like an error...
R-C aka beranger
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="006392.html">[Mageia-dev] ksnapshot conflicts with kdegraphics4-devel
</A></li>
<LI>Next message: <A HREF="006378.html">[Mageia-dev] [RPM] cauldron core/release logrotate-3.8.0-1.mga2
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6393">[ date ]</a>
<a href="thread.html#6393">[ thread ]</a>
<a href="subject.html#6393">[ subject ]</a>
<a href="author.html#6393">[ 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>
|
