summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101022/001326.html
blob: bb38f94d4ac42fcea717c73c047d53a557af03e3 (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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Mirror tree structure
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20tree%20structure&In-Reply-To=%3C20101022002648.143579f3%40werewolf.home%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   
   <LINK REL="Next"  HREF="001335.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Mirror tree structure</H1>
    <B>J.A. Magall&#243;n</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20tree%20structure&In-Reply-To=%3C20101022002648.143579f3%40werewolf.home%3E"
       TITLE="[Mageia-dev] Mirror tree structure">jamagallon at ono.com
       </A><BR>
    <I>Fri Oct 22 00:26:48 CEST 2010</I>
    <P><UL>
        
        <LI>Next message: <A HREF="001335.html">[Mageia-dev] Mirror tree structure
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1326">[ date ]</a>
              <a href="thread.html#1326">[ thread ]</a>
              <a href="subject.html#1326">[ subject ]</a>
              <a href="author.html#1326">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On Thu, 21 Oct 2010 17:16:06 +0100, Buchan Milne &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bgmilne at multilinks.com</A>&gt; wrote:

&gt;<i> On Thursday, 21 October 2010 06:37:37 Olivier Thauvin wrote:
</I>&gt;<i> &gt; * J.A. Magall&#243;n (<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">jamagallon at ono.com</A>) wrote:
</I>&gt;<i> &gt; &gt; On Wed, 20 Oct 2010 18:34:24 +0200, Olivier Thauvin 
</I>...
&gt;<i> &gt; 
</I>&gt;<i> &gt; &gt; - could be the arch names more uniform ? in my personal scripts/setups
</I>&gt;<i> &gt; &gt; 
</I>&gt;<i> &gt; &gt;   I use x86-32 and x86-64.
</I>&gt;<i> 
</I>&gt;<i> Is x86-32 a valid architecture for rpm etc.? While uniformity might be nice, 
</I>&gt;<i> unfortunately vendors don't necessarily choose uniform architecure names, and 
</I>&gt;<i> it might be better to match the repo structure to values that can be 
</I>&gt;<i> determined directly (and not heuristcally) . 
</I>&gt;<i> 
</I>&gt;<i> I've also never seen 'uname -m' report x86-32 or x86_32.
</I>&gt;<i> 
</I>&gt;<i> &gt; &gt;   Moreover, perhaps in a not so near future some
</I>&gt;<i> &gt; &gt;   adventurous soul builds Mageia on ARM or Sparc, so why not sort things
</I>&gt;<i> &gt; &gt;   like
</I>&gt;<i> &gt; &gt;   
</I>&gt;<i> &gt; &gt;     distrib/cauldron/srpm
</I>&gt;<i> &gt; &gt;     distrib/cauldron/x86/32/iso
</I>&gt;<i> &gt; &gt;     
</I>&gt;<i> &gt; &gt;                            /rpm
</I>&gt;<i> &gt; &gt;                         
</I>&gt;<i> &gt; &gt;                         /64
</I>&gt;<i> &gt; &gt;                     
</I>&gt;<i> &gt; &gt;                     /arm/32
</I>&gt;<i> &gt; &gt;                     
</I>&gt;<i> &gt; &gt;                         /64
</I>&gt;<i> 
</I>&gt;<i> I don't know if memory address space is a useful differentiator here, as 
</I>&gt;<i> features differ substantially in different ARM cores of the same family or 
</I>&gt;<i> architecture version. E.g., Fedora has an 'armv5tel' architecture, N900 ships 
</I>&gt;<i> .deb's with 'armel' as the architecture. See 
</I>&gt;<i> <A HREF="http://en.wikipedia.org/wiki/ARM_architecture">http://en.wikipedia.org/wiki/ARM_architecture</A>
</I>&gt;<i> 
</I>&gt;<i> &gt; &gt;                     
</I>&gt;<i> &gt; &gt;                     /sparc/32
</I>&gt;<i> &gt; &gt;                     
</I>&gt;<i> &gt; &gt;                           /64
</I>&gt;<i> 
</I>&gt;<i> AFAIK, the valid architecture names for sparc are sparc,sparc64,sparcv9.
</I>&gt;<i> 
</I>
I was just thinking of people navigating the tree structure looking for what
to download and install. Directory names have not to be the same as RPMs
architecture, isn't it ? And is more neutral, you can decide you build the
distro for Pentium3 at least and dont have to change the folder names... ;)

And, btw, what brain-damaged mind got the names i386 and x86_64 ? Solaris on
x86 uses i86pc (arch -k). Somebody should try to push upstream (in rpm, perhaps)
a decent naming scheme [x86,x86-32] - x86-64, [sparc,sparc-32] - sparc-64.
You said that fedora on ARM uses esoteric arch codes, couldn't be possible
to use x86-32 and try to get it into upstream RPM ?

Looking for that info (where that thing was born), I found that this naming
scheme (x86-32,x86-64) is even described in Wikipedia:

<A HREF="http://en.wikipedia.org/wiki/X86">http://en.wikipedia.org/wiki/X86</A>
<A HREF="http://en.wikipedia.org/wiki/X86_64">http://en.wikipedia.org/wiki/X86_64</A>

so it looks not so insane after all...

-- 
J.A. Magallon &lt;jamagallon()ono!com&gt;     \               Software is like sex:
                                         \         It's better when it's free
</PRE>



<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	
	<LI>Next message: <A HREF="001335.html">[Mageia-dev] Mirror tree structure
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1326">[ date ]</a>
              <a href="thread.html#1326">[ thread ]</a>
              <a href="subject.html#1326">[ subject ]</a>
              <a href="author.html#1326">[ 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>