From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-December/010469.html | 86 ++++++++++++++++++++++++++++ 1 file changed, 86 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-December/010469.html (limited to 'zarb-ml/mageia-dev/2011-December/010469.html') diff --git a/zarb-ml/mageia-dev/2011-December/010469.html b/zarb-ml/mageia-dev/2011-December/010469.html new file mode 100644 index 000000000..1adf980b1 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010469.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] How broken are RPM dependencies allowed to be? + + + + + + + + + +

[Mageia-dev] How broken are RPM dependencies allowed to be?

+ Dan Fandrich + dan at coneharvesters.com +
+ Thu Dec 15 10:36:49 CET 2011 +

+
+ +
On Wed, Dec 14, 2011 at 11:37:37PM +0100, nicolas vigier wrote:
+> Versionned dependencies are added when they are needed to allow correct
+> updates on stable release or upgrades from one release to an other
+> (installing all available updates, not only some of them), for example
+> to require installing some packages in the same transaction. Or when
+> the dependencies can be detected and added automatically. But I don't
+> think you should expect to be able to take any package from any release
+> and install it on an other release with accurate dependencies.
+
+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.
+
+>>> Dan
+
+ + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1