summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101103/001377.html
blob: 19775cf3dcccab1d18017e5c9f984f471645babd (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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Mirror list for apps (LONG mail)
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20list%20for%20apps%20%28LONG%20mail%29&In-Reply-To=%3CAANLkTimS1%2BEsM8vkmZADubtk4HCj41rQh%3DVNe6i_0%3DW1%40mail.gmail.com%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="001376.html">
   <LINK REL="Next"  HREF="001379.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Mirror list for apps (LONG mail)</H1>
    <B>Romain d'Alverny</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20list%20for%20apps%20%28LONG%20mail%29&In-Reply-To=%3CAANLkTimS1%2BEsM8vkmZADubtk4HCj41rQh%3DVNe6i_0%3DW1%40mail.gmail.com%3E"
       TITLE="[Mageia-dev] Mirror list for apps (LONG mail)">rdalverny at gmail.com
       </A><BR>
    <I>Wed Nov  3 20:04:59 CET 2010</I>
    <P><UL>
        <LI>Previous message: <A HREF="001376.html">[Mageia-dev] Mirror list for apps (LONG mail)
</A></li>
        <LI>Next message: <A HREF="001379.html">[Mageia-dev] Mirror list for apps (LONG mail)
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1377">[ date ]</a>
              <a href="thread.html#1377">[ thread ]</a>
              <a href="subject.html#1377">[ subject ]</a>
              <a href="author.html#1377">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On Wed, Nov 3, 2010 at 19:47, Olivier Thauvin
&lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">nanardon at nanardon.zarb.org</A>&gt; wrote:
[...]
&gt;<i> So, question and my own POV about this:
</I>&gt;<i> 1) /etc/product.id
</I>&gt;<i> &#160;* I don't like this file, I think it is redundant with
</I>&gt;<i> &#160; &#160;/etc/mandriva-release
</I>
It appeared for several reasons, in order to have a consistent scheme
to identify several Mandriva products: an ISO release, a specific
media, a set of media, a physical product, etc. It used to be spec'ed,
but not properly reviewed, neither strongly/fully implemented. See
<A HREF="http://wiki.mandriva.com/en/product_id">http://wiki.mandriva.com/en/product_id</A> (it never left the draft stage
actually).

It could have been only an int, or a hash string, putted against a
database to get a human readable label, but that would be then, less
human readable in the first place.

&gt;<i> &#160;* Why &quot;basic&quot; and not &quot;Free&quot; since it is the &quot;product&quot; flag ? Dunno
</I>&gt;<i> &#160;* Notice &quot;cooker&quot; does not appear in this file
</I>
It could. But here, provided it's a stable release, &quot;cooker&quot; is not
supposed to appear.

Given the new situation, I suggest to use a /etc/release file, somehow
like the /etc/mandriva-release file, but being strongly structured
(/etc/mandriva-release wasn't, in the long run), so we can have at
least:
 - product name (Mageia)
 - version
 - arch
 - branch (or something stating the unstable/stable release state)
 - build number (in case of automated builds, someday).

with mandatory ones being product name, version and arch.

&gt;<i> [...]
</I>&gt;<i> 3) The content
</I>&gt;<i> [...]
</I>&gt;<i> &#160;* Do we need specific line for update since now distribution include
</I>&gt;<i> &#160; &#160;everything
</I>
If we happen to have mirrors that only mirror an update tree?

&gt;<i> &#160;* Do we keep this format ?
</I>&gt;<i>
</I>&gt;<i> Keeping this format is more simple, just changing the line specifiying
</I>&gt;<i> basis url in URPMI.
</I>&gt;<i> By changing the the format we can add features, make it clearer, etc...
</I>&gt;<i> But changing format to what ? XML ? YAML ? CSV ? something worst ? :)
</I>&gt;<i> Changes can done later.
</I>
It's not an optimal format, but it looks simple and good enough. What
would be needed to extend/change it?


Romain
</PRE>



<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="001376.html">[Mageia-dev] Mirror list for apps (LONG mail)
</A></li>
	<LI>Next message: <A HREF="001379.html">[Mageia-dev] Mirror list for apps (LONG mail)
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1377">[ date ]</a>
              <a href="thread.html#1377">[ thread ]</a>
              <a href="subject.html#1377">[ subject ]</a>
              <a href="author.html#1377">[ 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>