diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2012-June/016922.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016922.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016922.html | 146 |
1 files changed, 146 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016922.html b/zarb-ml/mageia-dev/2012-June/016922.html new file mode 100644 index 000000000..083fa1928 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016922.html @@ -0,0 +1,146 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Backports Summary + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C4FEB1A85.8090307%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016920.html"> + <LINK REL="Next" HREF="016927.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Backports Summary</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C4FEB1A85.8090307%40laposte.net%3E" + TITLE="[Mageia-dev] Backports Summary">andre999mga at laposte.net + </A><BR> + <I>Wed Jun 27 16:36:53 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016920.html">[Mageia-dev] Backports Summary +</A></li> + <LI>Next message: <A HREF="016927.html">[Mageia-dev] Backports Summary +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16922">[ date ]</a> + <a href="thread.html#16922">[ thread ]</a> + <a href="subject.html#16922">[ subject ]</a> + <a href="author.html#16922">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>nicolas vigier a écrit : +><i> On Wed, 27 Jun 2012, andre999 wrote: +</I>><i> +</I>><i> +</I>>><i> Thomas Backlund a écrit : +</I>>><i> +</I>>>><i> andre999 skrev 27.6.2012 14:40: +</I>>>><i> +</I>>>>><i> Thomas Backlund a écrit : +</I>>>>><i> +</I>>>>>><i> andre999 skrev 27.6.2012 10:47: +</I>>>>>><i> +</I>>>><i> +</I>>>>>>><i> I would favour adding the requirement that the dependancies of the +</I>>>>>>><i> backport must be available in the next release. So that we would +</I>>>>>>><i> expect +</I>>>>>>><i> +</I>>>>>><i> +</I>>>>>><i> This is esentially stating that we cant backport any bigger version to +</I>>>>>><i> mga2 /backports than mga3 will havein /release wich means when we hit +</I>>>>>><i> version freeze for mga3, it also freezes mga2 /backports... +</I>>>>>><i> +</I>>>>><i> I'm not following this point. +</I>>>>><i> What I mean is that if backport xx for mga1 requires yy version 12 in +</I>>>>><i> mga1, but yy is version 13 in mga2, we would define the requires for yy +</I>>>>><i> to accept versions 12 to 13 (or maybe wider). +</I>>>>><i> +</I>>>><i> Point is what if you backport version 14 to mga1, and mga2 has version 13, +</I>>>><i> then upgrade path breaks. +</I>>>><i> +</I>>><i> No problem. If the requirements of version 14 are present in mga2, then +</I>>><i> the backport will (very likely) continue to work normally. If the versions +</I>>><i> of the required packages change, they will be updated with the upgrade. +</I>>><i> Since version 13 of mga2 is less than the version 14 of the backport, it +</I>>><i> won't be installed. +</I>>><i> +</I>><i> There is no guaranty that requirements of version 14 mga1 backports are +</I>><i> all available in mageia 2. If it is linked with libsomething.so.1, but +</I>><i> mageia 2 only has libsomething.so.2, then there is a problem. +</I>><i> +</I>><i> +</I>That was my point. +I was suggesting that it be required that backport requires be +compatible with newer releases. +In your example, cauldron would probably require the libsomething.so.2, +so if the backport requires could be adjusted to work with +libsomething.so.1, we would keep the requires compatible with +libsomething.so.2. If that isn't possible, then it wouldn't be accepted. +I'm no expert of course, but it seems to me that it would be generally +possible as long as there weren't important code changes made to make +the backport work. +So it would largely be a question of appropriately adjusting the +specified requires. + +-- +André + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016920.html">[Mageia-dev] Backports Summary +</A></li> + <LI>Next message: <A HREF="016927.html">[Mageia-dev] Backports Summary +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16922">[ date ]</a> + <a href="thread.html#16922">[ thread ]</a> + <a href="subject.html#16922">[ subject ]</a> + <a href="author.html#16922">[ 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> |