blob: 1adf980b1e03aecb7f3dad2ecf1dcc56e23bb57e (
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
80
81
82
83
84
85
86
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] How broken are RPM dependencies allowed to be?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20broken%20are%20RPM%20dependencies%20allowed%20to%20be%3F&In-Reply-To=%3C20111215093647.GA29774%40coneharvesters.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="010451.html">
<LINK REL="Next" HREF="010473.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] How broken are RPM dependencies allowed to be?</H1>
<B>Dan Fandrich</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20broken%20are%20RPM%20dependencies%20allowed%20to%20be%3F&In-Reply-To=%3C20111215093647.GA29774%40coneharvesters.com%3E"
TITLE="[Mageia-dev] How broken are RPM dependencies allowed to be?">dan at coneharvesters.com
</A><BR>
<I>Thu Dec 15 10:36:49 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="010451.html">[Mageia-dev] How broken are RPM dependencies allowed to be?
</A></li>
<LI>Next message: <A HREF="010473.html">[Mageia-dev] How broken are RPM dependencies allowed to be?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10469">[ date ]</a>
<a href="thread.html#10469">[ thread ]</a>
<a href="subject.html#10469">[ subject ]</a>
<a href="author.html#10469">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Wed, Dec 14, 2011 at 11:37:37PM +0100, nicolas vigier wrote:
><i> Versionned dependencies are added when they are needed to allow correct
</I>><i> updates on stable release or upgrades from one release to an other
</I>><i> (installing all available updates, not only some of them), for example
</I>><i> to require installing some packages in the same transaction. Or when
</I>><i> the dependencies can be detected and added automatically. But I don't
</I>><i> think you should expect to be able to take any package from any release
</I>><i> and install it on an other release with accurate dependencies.
</I>
This is exactly the kind of policy statement I was hoping to find somewhere.
If this is the consensus, I'm happy to update the wiki with this added
detail.
But when you say "from one release to another", presumably you want to
limit how many releases back you want to bother supporting. There's not
much point in checking for a minimum version that hasn't shipped for 5 years.
>>><i> Dan
</I></PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="010451.html">[Mageia-dev] How broken are RPM dependencies allowed to be?
</A></li>
<LI>Next message: <A HREF="010473.html">[Mageia-dev] How broken are RPM dependencies allowed to be?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10469">[ date ]</a>
<a href="thread.html#10469">[ thread ]</a>
<a href="subject.html#10469">[ subject ]</a>
<a href="author.html#10469">[ 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>
|