blob: 83e81a95b571d8932deed36a72375acc31e47cd2 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
|
<!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=%3C4EDD4C19.2090302%40mageia.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="010211.html">
<LINK REL="Next" HREF="010213.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] RFC: Opening Backports (once again...)</H1>
<B>Thomas Backlund</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=%3C4EDD4C19.2090302%40mageia.org%3E"
TITLE="[Mageia-dev] RFC: Opening Backports (once again...)">tmb at mageia.org
</A><BR>
<I>Mon Dec 5 23:56:25 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="010211.html">[Mageia-dev] [177078] Add README.urpmi to note that apache needs to be running
</A></li>
<LI>Next message: <A HREF="010213.html">[Mageia-dev] RFC: Opening Backports (once again...)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10212">[ date ]</a>
<a href="thread.html#10212">[ thread ]</a>
<a href="subject.html#10212">[ subject ]</a>
<a href="author.html#10212">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>
Now,
here comes the question about backports once again.
We are now 6+ months into Mageia 1, and we are nowhere closer to opening
backports that we were at Mageia 1 release time.
Because of that there are 3rdparty repos popping up everywhere...,
something we hoped to avoid atleast partly when starting this project.
And at current rate we will probably release Mageia "infinity"
before backports is opened.
It has been delayed because of needed infrastructure changes,
something no-one have had time to do so far...
I know there is "only some coding missing" and "someone should
do it", buth truthfully there are only a few that knows the
code used in the buildsystem enough to actually make it happend,
and they are already othervise busy or overloaded...
(this is no rant against them, as all here are using their
personal free time to help out)
And to be honest I dont see that changing anytime soon...
So here is a suggestion to get some value to our endusers:
we add a backports branch on svn
So packages for backports would use:
svn.mageia.org/packages/backports/1/<package>/{current,pristine,releases}
and allow that to be used for backports.
Using a separate branch is also a cleaner way of providing
backports, and makes it easy to separate changes needed only
for Cauldron (or backports).
--
Thomas
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="010211.html">[Mageia-dev] [177078] Add README.urpmi to note that apache needs to be running
</A></li>
<LI>Next message: <A HREF="010213.html">[Mageia-dev] RFC: Opening Backports (once again...)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10212">[ date ]</a>
<a href="thread.html#10212">[ thread ]</a>
<a href="subject.html#10212">[ subject ]</a>
<a href="author.html#10212">[ 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>
|
