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/016334.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/016334.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016334.html | 159 |
1 files changed, 159 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016334.html b/zarb-ml/mageia-dev/2012-June/016334.html new file mode 100644 index 000000000..a343f1c61 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016334.html @@ -0,0 +1,159 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Backports policy clarification (and discussion) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20clarification%20%28and%20discussion%29&In-Reply-To=%3C4FD43A7E.40400%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016328.html"> + <LINK REL="Next" HREF="016327.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Backports policy clarification (and discussion)</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20clarification%20%28and%20discussion%29&In-Reply-To=%3C4FD43A7E.40400%40laposte.net%3E" + TITLE="[Mageia-dev] Backports policy clarification (and discussion)">andre999mga at laposte.net + </A><BR> + <I>Sun Jun 10 08:11:10 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016328.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI>Next message: <A HREF="016327.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16334">[ date ]</a> + <a href="thread.html#16334">[ thread ]</a> + <a href="subject.html#16334">[ subject ]</a> + <a href="author.html#16334">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Thomas Backlund a écrit : +><i> 09.06.2012 13:29, andre999 skrev: +</I>><i> +</I>>><i> OK. To backport from Cauldron to mga1, we have to backport from +</I>>><i> Cauldron to mga2, (bumping the revision in cauldron to ensure that is is +</I>>><i> higher), then backport from mga2 to mga1, ensuring that the revision is +</I>>><i> lower in mga1 than in mga2. (e.g. revision x.1 in cauldron, x.0.1 in +</I>>><i> mga2, x.0.0.1 in mga1) Pretty straight forward. +</I>>><i> +</I>>><i> +</I>><i> Not needed as 1.mgaX> 1.mga3> 1.mga2> 1.mga1 +</I>><i> +</I> +I was thinking of available packages changing between mga1 and mga2, but +if the backport is installed (with whatever requires being installed), +these requires wouldn't (or shouldn't) be removed with a release update +from mga1 to mga2. + +But what do we do if a package required for installing the backport in +mga1 is not available due to conflicts in mga2 ? Do we assume that the +conflicting package in mga2 has the appropriate provides, or even can +provide the required function ? +Or do we try to detect such situations and remove the backport in question ? + +If we make a point of making a backport for mga2 (or upgrade if it +doesn't have to be a backport in mga2), then this problem would already +be resolved. +Of course, most of the time this wouldn't be a problem, and we could +check for requires that are not available in mga2. +Another thing that we should verify is the version specified for +requires. That is very likely to change between release versions. + +Maybe a rule that the requires specified for the backport in the target +release should be compatible with Cauldron. +That is, that all packages required for the backport in the target +release are provided in Cauldron (either by provides or the specific +package), and that the versions specified - if any - are compatible with +the versions available in Cauldron (and of course the target release). +This should ensure that the requires would be available in any interim +releases. + +>><i> - Cherry-picking refers to the users' option to install a backport, +</I>>><i> which has nothing to do with the packaging itself. +</I>>><i> +</I>>><i> +</I>><i> Oh but it has _everything_ to do with packaging... +</I>><i> +</I>><i> in order for cherrypicking to work, the deps must be stricter so +</I>><i> that any deps in backports gets selected along with the package +</I>><i> the user is selecting. +</I>><i> +</I> +I was assuming that the requires would be well defined for a backport, +as they should be for any package. + +It would be nice to have a tool to check for dependancies, if there +isn't one already. +To avoid overlooking something because the test systems have some of the +dependancies already installed. Particularly since QA would be less +implicated in the testing. +><i> -- +</I>><i> Thomas +</I>><i> +</I>><i> +</I>-- +André + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016328.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI>Next message: <A HREF="016327.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16334">[ date ]</a> + <a href="thread.html#16334">[ thread ]</a> + <a href="subject.html#16334">[ subject ]</a> + <a href="author.html#16334">[ 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> |