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/016935.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/016935.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016935.html | 202 |
1 files changed, 202 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016935.html b/zarb-ml/mageia-dev/2012-June/016935.html new file mode 100644 index 000000000..db0e94c8f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016935.html @@ -0,0 +1,202 @@ +<!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=%3C4FEB46EE.5010608%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016927.html"> + <LINK REL="Next" HREF="016937.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=%3C4FEB46EE.5010608%40laposte.net%3E" + TITLE="[Mageia-dev] Backports Summary">andre999mga at laposte.net + </A><BR> + <I>Wed Jun 27 19:46:22 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016927.html">[Mageia-dev] Backports Summary +</A></li> + <LI>Next message: <A HREF="016937.html">[Mageia-dev] Backports Summary +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16935">[ date ]</a> + <a href="thread.html#16935">[ thread ]</a> + <a href="subject.html#16935">[ subject ]</a> + <a href="author.html#16935">[ 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> nicolas vigier a écrit : +</I>>><i> +</I>>>><i> On Wed, 27 Jun 2012, andre999 wrote: +</I>>>><i> +</I>>>><i> +</I>>>><i> +</I>>>>><i> Thomas Backlund a écrit : +</I>>>>><i> +</I>>>>><i> +</I>>>>>><i> andre999 skrev 27.6.2012 14:40: +</I>>>>>><i> +</I>>>>>><i> +</I>>>>>>><i> Thomas Backlund a écrit : +</I>>>>>>><i> +</I>>>>>>><i> +</I>>>>>>>><i> andre999 skrev 27.6.2012 10:47: +</I>>>>>>>><i> +</I>>>>>>>><i> +</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>>>>>>><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> +</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> +</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> +</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>>>><i> +</I>>><i> That was my point. +</I>>><i> I was suggesting that it be required that backport requires be compatible +</I>>><i> with newer releases. +</I>>><i> +</I>><i> And how do you check that it is compatible, without testing ? And how do +</I>><i> you test that it will be compatible with a newer release that is not yet +</I>><i> released ? +</I>><i> +</I> +You split in the middle of the point. (The above sentence could have +been better worded.) +See below. +><i> Maybe we can also require that backports are bugfree, so we don't have +</I>><i> to manage backport updates. +</I>><i> +</I> +That would be nice, if you can see how to do it :D +><i> +</I>>><i> In your example, cauldron would probably require the libsomething.so.2, so +</I>>><i> if the backport requires could be adjusted to work with libsomething.so.1, +</I>>><i> we would keep the requires compatible with libsomething.so.2. If that +</I>>><i> isn't possible, then it wouldn't be accepted. +</I>>><i> +</I>><i> We cannot link a program with both libsomething.so.1 and +</I>><i> libsomething.so.2. +</I>><i> +</I> +If the spec file requires cannot be adjusted to accept linking with +whichever of the 2 is available, then in that case the backport wouldn't +be accepted - if my suggested restriction is accepted. + +>><i> I'm no expert of course, but it seems to me that it would be generally +</I>>><i> possible as long as there weren't important code changes made to make the +</I>>><i> backport work. +</I>>><i> So it would largely be a question of appropriately adjusting the specified +</I>>><i> requires. +</I>>><i> +</I>><i> A lot of requires are generated automatically, we cannot change them +</I>><i> (and changing them would probably be wrong). And a lot of requires are +</I>><i> not versionned, but implicitly require the version available in the +</I>><i> same mageia release, without any guaranty that it works with a different +</I>><i> version. +</I>><i> +</I> +You mean generated automatically in the spec file ? Surprising. +If the require isn't versioned, since it would work in cauldron, and +also works in the backport release, then I would expect that it would +work in interim releases. If it doesn't, that is in the risk of a backport. + +Don't forget, my suggestion is to increase the _probability_ that a +backport will work in interim releases. Not to garantee that it will. +In my experience, it is essentially the unavailability of required +packages that makes a package from an older release stop working. A +backport would fit in this mold, except it will be a variation of what +is already working in cauldron. +Collectively we may think it is not worth the increased reliability of +backports, but I think that for little effort we see an important gain. + +-- +André + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016927.html">[Mageia-dev] Backports Summary +</A></li> + <LI>Next message: <A HREF="016937.html">[Mageia-dev] Backports Summary +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16935">[ date ]</a> + <a href="thread.html#16935">[ thread ]</a> + <a href="subject.html#16935">[ subject ]</a> + <a href="author.html#16935">[ 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> |