diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-December/010310.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-December/010310.html | 177 |
1 files changed, 177 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-December/010310.html b/zarb-ml/mageia-dev/2011-December/010310.html new file mode 100644 index 000000000..ff6b4fe98 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010310.html @@ -0,0 +1,177 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] RFC: Opening Backports (once again...) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%3A%20Opening%20Backports%20%28once%20again...%29&In-Reply-To=%3C1323516732.3757.58.camel%40localhost%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="010308.html"> + <LINK REL="Next" HREF="010314.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] RFC: Opening Backports (once again...)</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%3A%20Opening%20Backports%20%28once%20again...%29&In-Reply-To=%3C1323516732.3757.58.camel%40localhost%3E" + TITLE="[Mageia-dev] RFC: Opening Backports (once again...)">misc at zarb.org + </A><BR> + <I>Sat Dec 10 12:32:12 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="010308.html">[Mageia-dev] RFC: Opening Backports (once again...) +</A></li> + <LI>Next message: <A HREF="010314.html">[Mageia-dev] RFC: Opening Backports (once again...) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10310">[ date ]</a> + <a href="thread.html#10310">[ thread ]</a> + <a href="subject.html#10310">[ subject ]</a> + <a href="author.html#10310">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le mardi 06 décembre 2011 à 00:56 +0200, Thomas Backlund a écrit : +><i> Now, +</I>><i> +</I>><i> here comes the question about backports once again. +</I>><i> +</I>><i> We are now 6+ months into Mageia 1, and we are nowhere closer to opening +</I>><i> backports that we were at Mageia 1 release time. +</I>><i> +</I>><i> Because of that there are 3rdparty repos popping up everywhere..., +</I>><i> something we hoped to avoid atleast partly when starting this project. +</I> +Well, the backport issue ( ie : +- no garantee of keep the distribution upgradable +- no security ) + +have also not been fixed, so that's rather unfair to + +><i> And at current rate we will probably release Mageia "infinity" +</I>><i> before backports is opened. +</I>><i> +</I>><i> +</I>><i> It has been delayed because of needed infrastructure changes, +</I>><i> something no-one have had time to do so far... +</I>><i> +</I>><i> I know there is "only some coding missing" and "someone should +</I>><i> do it", buth truthfully there are only a few that knows the +</I>><i> code used in the buildsystem enough to actually make it happend, +</I>><i> and they are already othervise busy or overloaded... +</I>><i> (this is no rant against them, as all here are using their +</I>><i> personal free time to help out) +</I>><i> +</I>><i> And to be honest I dont see that changing anytime soon... +</I> +Then we have a bigger problem to solve. + +><i> So here is a suggestion to get some value to our endusers: +</I>><i> +</I>><i> we add a backports branch on svn +</I>><i> +</I>><i> So packages for backports would use: +</I>><i> +</I>><i> svn.mageia.org/packages/backports/1/<package>/{current,pristine,releases} +</I>><i> +</I>><i> and allow that to be used for backports. +</I>><i> +</I>><i> Using a separate branch is also a cleaner way of providing +</I>><i> backports, and makes it easy to separate changes needed only +</I>><i> for Cauldron (or backports). +</I> +Then in practice, that mean having a 2nd/3rd distribution ( because +there is a separate 2nd svn branch, and a 3rd one for later ) and so +that's a big no for me. Having 2+ branchs is just asking for trouble +when they are not in sync ( and since keeping everything in sync +properly with svn is a pain if there is a divergence, this will not be +done ). + +Worst, if we do like in mdv and propose 2 way of backporting ( submit +from cauldron, submit from a branch ), this will create a mess of having +some packages from cauldron, some from the branch, and people having no +way from knowing where does a package come from. This also make the +system harder to maintain and to follow, and rather impossible to script +properly. + +So that's also to be avoided. + +Having a separate branch where people can write also remove the only +incentive I have seen for backports, ie, wider testing of our packages, +because they may not really the same as in cauldron. + + +So here is what I propose : + +- have X branchs, but do not let anyone commit on it, besides a system +user. When a package is submitted to cauldron, it is also copied to this +branch, ie, we make sure current is in sync. The same goes for version +N-1 being copied from N once a backported rpm have been submitted to be +used by people. Once a distribution is no longer supported, we close the +branch, and disable the sync. + +- backports are only submitted from the branch, with separate +markrelease, tags, whatever. This let us have proper audit of backports, +and who did what. + +- packagers still need to commit and submit on cauldron before any +backports. So we miss no fixes or anything by mistake. We also make sure +that cauldron is always the highest version possible, thus permitting at +least some form of upgrade. ( either stable to stable, provided +backports are used, or stable to cauldron ). And we also ensure that +backports are done first on the most recent stable version, for the same +reason ( ensure some form of upgrade path, as asked several time by +users ). + +And we can still use %ifdef if a need arise for a different spec between +distribution versions. While that make spec less readable, that's more +readable than having forked specs 2 or 3 times. + +This requires : + +- 1 youri action to copy the package to current backport branch ( can be +done based on the markrelease action and the others ) + +- 1 svn configuration to prevent people from writing directly there ( or +just say to not do it, and burn people who do it ) + +- youri config to let people submit from backports to backports_testing. + + +-- +Michael Scherer + +</PRE> + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="010308.html">[Mageia-dev] RFC: Opening Backports (once again...) +</A></li> + <LI>Next message: <A HREF="010314.html">[Mageia-dev] RFC: Opening Backports (once again...) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10310">[ date ]</a> + <a href="thread.html#10310">[ thread ]</a> + <a href="subject.html#10310">[ subject ]</a> + <a href="author.html#10310">[ 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> |