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
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Mirror layout, round two
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C4CF14731.8020007%40iki.fi%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="001465.html">
<LINK REL="Next" HREF="001460.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Mirror layout, round two</H1>
<B>Thomas Backlund</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C4CF14731.8020007%40iki.fi%3E"
TITLE="[Mageia-dev] Mirror layout, round two">tmb at iki.fi
</A><BR>
<I>Sat Nov 27 19:00:17 CET 2010</I>
<P><UL>
<LI>Previous message: <A HREF="001465.html">[Mageia-dev] Mirror layout, round two
</A></li>
<LI>Next message: <A HREF="001460.html">[Mageia-dev] Mirror layout, round two
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1467">[ date ]</a>
<a href="thread.html#1467">[ thread ]</a>
<a href="subject.html#1467">[ subject ]</a>
<a href="author.html#1467">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Michael scherer skrev 27.11.2010 10:43:
><i> On Fri, Nov 26, 2010 at 10:29:14PM +0200, Thomas Backlund wrote:
</I>[...]
>><i>
</I>>><i> Then we come to the "problematic" part:
</I>><i>
</I>><i> This part look really too complex to me.
</I>><i>
</I>>><i> ------
</I>>><i> /x86_64/
</I>>><i> /media/
</I>>><i> /codecs/ (disabled by default)
</I>><i>
</I>><i> so, ogg, webm, being codec, should go there or not ?
</I>><i> What about patents problem about something else than codec ?
</I>><i> ( freetype, image such as gif, DRM stuff )
</I>><i>
</I>
Actually this is the "maybe_legal_greyzone" repo,
but since flagging it as "codecs" would really make people
react, I named it so for now...
>><i> /core/ (old main+contrib)
</I>>><i> /backports/ (disabled by default)
</I>>><i> /backports_testing/ (disabled by default)
</I>>><i> /release/
</I>>><i> /testing/ (disabled by default)
</I>>><i> /updates/
</I>>><i> /extra/ (unmaintained, disabled by default)
</I>><i>
</I>><i> If used by people, then why no one step to maintain anything ?
</I>
Yeah, thats the problem.
And reality shows we have a lot of packages assigned to nomaintainer@ ...
><i> If someone take the maintainace, does it mean that we will move the package ?
</I>><i>
</I>
Yes.
And if a package in /core/ gets orphaned, it will be moved to /extra/
after a "grace period" of a month or so...
>><i> /firmware/ (disabled by default)
</I>><i>
</I>><i> Why separate firmware from non_free ? What does it bring ?
</I>><i> Since both of them are disabled by default, they can be simply merged.
</I>><i>
</I>
Well, this suggestion is partly based on the fact that we have users
that want a firmware free install, wich this would satisfy...
But yes, if we ignore those suggestions, we split the firmwares in GPL
-> /core/ and the rest to /non-free/
>><i> /games/ (disabled by default)
</I>><i>
</I>><i> That's a simplification that make no sense.
</I>><i> Not all games are big, not all big packages are games ( tetex, openoffice ).
</I>
It's not only a size question, its also a nice option for companies to
not mirror games ("employees should work, not play...")
And we have some contributors that already have stated that they plan to
add all possible games so it will grow.
and we all know games are the fastest growing /space demanding...
><i>
</I>><i> This only bring complexity on our side, complexity on mirror side, and
</I>><i> bring few improvement to users. A rather more precise label would be to have
</I>><i> /contents/ repository, as this is not the game that take space, but the content.
</I>><i>
</I>><i> And a explicit policy of splitting content from big packages, with a explicit size or
</I>><i> expected size for limit ( like if the package is more than 100 mo ). That's also a media
</I>><i> where deltarpm would make sense, or someting like that. In the mean time this would
</I>><i> only bring complexity to everybody else.
</I>><i>
</I>>><i> /non-free/ (disabled by default)
</I>>><i> /debug_*/ (disabled by default)
</I>><i>
</I>><i>
</I>><i> And what are the relation of requirements ?
</I>><i> Ie, what can requires non_free, codecs, games, etc ?
</I>><i>
</I>
IMHO /core/ should be selfcontained.
We are promoting open source after all.
><i> And what about something that can goes in both media, ie a non_free
</I>><i> game goes where ? A unmaintained codecs goes where ?
</I>
Yeah, to be precise, that would need a games_non-free
For codecs either a extra_codecs or simply drop after a grace period.
but I guess codecs are important to people, so hopefully they wont get
orphaned...
--
Thomas
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001465.html">[Mageia-dev] Mirror layout, round two
</A></li>
<LI>Next message: <A HREF="001460.html">[Mageia-dev] Mirror layout, round two
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1467">[ date ]</a>
<a href="thread.html#1467">[ thread ]</a>
<a href="subject.html#1467">[ subject ]</a>
<a href="author.html#1467">[ 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>
|
