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/2011-December/010215.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/2011-December/010215.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-December/010215.html | 182 |
1 files changed, 182 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-December/010215.html b/zarb-ml/mageia-dev/2011-December/010215.html new file mode 100644 index 000000000..de94d8694 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010215.html @@ -0,0 +1,182 @@ +<!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=%3C4EDD53BF.5000806%40mageia.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="010213.html"> + <LINK REL="Next" HREF="010219.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] RFC: Opening Backports (once again...)</H1> + <B>Anssi Hannula</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=%3C4EDD53BF.5000806%40mageia.org%3E" + TITLE="[Mageia-dev] RFC: Opening Backports (once again...)">anssi at mageia.org + </A><BR> + <I>Tue Dec 6 00:29:03 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="010213.html">[Mageia-dev] RFC: Opening Backports (once again...) +</A></li> + <LI>Next message: <A HREF="010219.html">[Mageia-dev] RFC: Opening Backports (once again...) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10215">[ date ]</a> + <a href="thread.html#10215">[ thread ]</a> + <a href="subject.html#10215">[ subject ]</a> + <a href="author.html#10215">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 06.12.2011 00:56, Thomas Backlund wrote: +><i> +</I>><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>><i> +</I>><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> +The biggest problem for me is that it is really difficult to test any +changes, one'd need a mockup of the whole buildsystem... and I don't +want to propose any patches blind :) + +><i> And to be honest I dont see that changing anytime soon... +</I>><i> +</I>><i> +</I>><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> +Hm, how does this help with enabling backports (i.e. compared to simply +using cauldron repo)? + +Anyway, would the above branch work like this: + +e.g. lets imagine I want to, in order: +1. provide foobar 1.1 to backports. +2. cauldron foobar upgraded to 1.2, some patches added, some removed, + and other changes +3. provide foobar 1.2 to backports +4. 1.3 to cauldron and backports + +To backport foobar 1.1, I guess I'd simply do + svn copy svn+<A HREF="ssh://svn.mageia.org/svn/packages/cauldron/foobar">ssh://svn.mageia.org/svn/packages/cauldron/foobar</A> \ + svn+<A HREF="ssh://svn.mageia.org/svn/packages/backports/1/foobar">ssh://svn.mageia.org/svn/packages/backports/1/foobar</A> +and then the submit command. + +When time comes to provide foobar 1.2 to backports, the options are: +Option 1: + svn del svn+<A HREF="ssh://svn.mageia.org/svn/packages/backports/1/foobar">ssh://svn.mageia.org/svn/packages/backports/1/foobar</A> + svn copy svn+<A HREF="ssh://svn.mageia.org/svn/packages/cauldron/foobar">ssh://svn.mageia.org/svn/packages/cauldron/foobar</A> \ + svn+<A HREF="ssh://svn.mageia.org/svn/packages/backports/1/foobar">ssh://svn.mageia.org/svn/packages/backports/1/foobar</A> + and submit. Changelog is the same as in cauldron. + +Option 2: + svn checkout \ + svn+<A HREF="ssh://svn.mageia.org/svn/packages/backports/1/foobar/current">ssh://svn.mageia.org/svn/packages/backports/1/foobar/current</A> \ + foobar + cd foobar && svn merge -r prevrev:HEAD \ + svn+<A HREF="ssh://svn.mageia.org/svn/packages/cauldron/foobar/current">ssh://svn.mageia.org/svn/packages/cauldron/foobar/current</A> + svn commit + # copy all the log entries from the cauldron interval to the log msg + and submit. + Note: results in broken changelogs unless one does manual + markreleases, but changelogs are already broken both in mga1 updates + and in cauldron (youri issue [1]). This is more notable here, though, + as backports happen generally more often multiple times than updates. + +Repeat with 1.3. + +Correct? + +[1] <A HREF="https://bugs.mageia.org/show_bug.cgi?id=2633">https://bugs.mageia.org/show_bug.cgi?id=2633</A> + +-- +Anssi Hannula +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="010213.html">[Mageia-dev] RFC: Opening Backports (once again...) +</A></li> + <LI>Next message: <A HREF="010219.html">[Mageia-dev] RFC: Opening Backports (once again...) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10215">[ date ]</a> + <a href="thread.html#10215">[ thread ]</a> + <a href="subject.html#10215">[ subject ]</a> + <a href="author.html#10215">[ 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> |