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
|
<!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=%3C4CF2C54A.7040509%40iki.fi%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="001476.html">
<LINK REL="Next" HREF="001478.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=%3C4CF2C54A.7040509%40iki.fi%3E"
TITLE="[Mageia-dev] Mirror layout, round two">tmb at iki.fi
</A><BR>
<I>Sun Nov 28 22:10:34 CET 2010</I>
<P><UL>
<LI>Previous message: <A HREF="001476.html">[Mageia-dev] Mirror layout, round two
</A></li>
<LI>Next message: <A HREF="001478.html">[Mageia-dev] Mirror layout, round two
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1477">[ date ]</a>
<a href="thread.html#1477">[ thread ]</a>
<a href="subject.html#1477">[ subject ]</a>
<a href="author.html#1477">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Renaud MICHEL skrev 28.11.2010 22:54:
><i> On dimanche 28 novembre 2010 at 21:12, Thomas Backlund wrote :
</I>>><i> So the mirror medias accordingly to all comments so far would be a
</I>>><i> simple:
</I>>><i>
</I>>><i> * core
</I>>><i> - enabled by default
</I>>><i> - mirrors must mirror this media to be listed as a mirror
</I>>><i> - only GPL stuff
</I>><i>
</I>><i> I guess you meant free (as defined by FSF, or we can make our own
</I>><i> definition, like debian), we surely don't want to restrict ourself to GPL-
</I>><i> only stuff.
</I>
Yeah. I meant to change that.
I do mean free/libre as in FSF/OSI definition.
><i>
</I>>><i> - must be selfcontained
</I>>><i>
</I>>><i> * nonfree
</I>>><i> - disabled by default, installer will ask to enable it if
</I>>><i> it detects hw that need driver/fw from here...
</I>>><i> - mirrors must mirror this media to be listed as a mirror
</I>>><i> - contains apps/drivers/firmware that are free to redistribute,
</I>>><i> but we dont have GPL source for
</I>>><i> - for example ati/nvidia drivers/firmware, Oracle Java, ...
</I>>><i>
</I>>><i> * tainted
</I>>><i> - disabled by default
</I>>><i> - mirrors are free to not mirror this media
</I>>><i> - stuff we think we can redistribute, but that may have some
</I>>><i> patent issues or other restrictions in oter countries.
</I>><i>
</I>><i> Merging "codecs" and "firmware" into "tainted" makes sense.
</I>><i>
</I>
actually most firmware we have would end up in core or nonfree
><i> So "games" and "extra" gets merged back into core (except for non-free games
</I>><i> of course), won't this make an enormous repos?
</I>><i>
</I>
People seemed to dislike the games splitout, so I "merged" it again
><i> I think it was better to have a separated games repos, as it will quickly
</I>><i> get big, and is likely to have frequent backports (as gamers generally want
</I>><i> to have the latest release).
</I>><i>
</I>
Well, if we want to split out games, it needs atleast:
* games
* games_nonfree
><i> Would it be possible to have a separate games sub-project, that won't freeze
</I>><i> to make releases with the rest of mageia?
</I>><i> Instead it would be an always updating repos which is compiled with the
</I>><i> latest stable release (or even the previous, if it is possible to have
</I>><i> packages that install correctly on both).
</I>><i> The project would only have a "testing" and "release" (or another name to
</I>><i> avoid confusion with other "release" repos which are frozen), this way you
</I>><i> could quickly have new versions of all the games, if they don't need
</I>><i> bleeding-edge libraries (I think they rarely does).
</I>><i>
</I>
Interesting idea, but problem is that if the games are built against
some newer system libs, they'll stop working on older releases...
--
Thomas
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001476.html">[Mageia-dev] Mirror layout, round two
</A></li>
<LI>Next message: <A HREF="001478.html">[Mageia-dev] Mirror layout, round two
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1477">[ date ]</a>
<a href="thread.html#1477">[ thread ]</a>
<a href="subject.html#1477">[ subject ]</a>
<a href="author.html#1477">[ 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>
|
