blob: 587e0ccac50164a2ed731bad99ac8d2951b33f1c (
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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-discuss] Mageia Mirror size
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Mageia%20Mirror%20size&In-Reply-To=%3Cm3sk0nkl42.fsf%40euphor.blino.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="002064.html">
<LINK REL="Next" HREF="002067.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-discuss] Mageia Mirror size</H1>
<B>Olivier Blin</B>
<A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Mageia%20Mirror%20size&In-Reply-To=%3Cm3sk0nkl42.fsf%40euphor.blino.org%3E"
TITLE="[Mageia-discuss] Mageia Mirror size">mageia at blino.org
</A><BR>
<I>Sun Oct 3 23:43:57 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="002064.html">[Mageia-discuss] Mageia Mirror size
</A></li>
<LI>Next message: <A HREF="002067.html">[Mageia-discuss] Mageia Mirror size
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2074">[ date ]</a>
<a href="thread.html#2074">[ thread ]</a>
<a href="subject.html#2074">[ subject ]</a>
<a href="author.html#2074">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Olivier Thauvin <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">nanardon at nanardon.zarb.org</A>> writes:
><i> * Olivier Blin (<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">mageia at blino.org</A>) wrote:
</I>>><i> Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">misc at zarb.org</A>> writes:
</I>>><i>
</I>>><i> >> Yes, noarch are supposed to be hardlinked already.
</I>>><i> >> But it could make the upload process simpler to have noarch in a
</I>>><i> >> separate directory (no need to hardlink to all arches), and genhdlist2
</I>>><i> >> faster (by splitting out a noarch hdlist).
</I>>><i> >
</I>>><i> > But this requires all arch to be synced.
</I>>><i> > While we achieved this for x86 and x86_64, this was not the case in the
</I>>><i> > past for sparc and ppc. Given the fact that arm is surely gonna play a
</I>>><i> > important role, what would be the impact on various non synced ports of
</I>>><i> > Mageia, if any ?
</I>>><i>
</I>>><i> Why would they be unsynced?
</I>>><i> If we have a separate directory for noarch, it could be shared by all
</I>>><i> arches, which means there would be no such unsync issue.
</I>><i>
</I>><i> The problem will occurs if new noarch come from i586/x86_64 whereas
</I>><i> another arch is no longer updated. Some dependencies will get broken
</I>><i> between noarch <=> arch rpms (foo -arch- requires bar = 1 -noarch- and
</I>><i> bar get update to version 2 for exemple).
</I>
Well, we have to assume that all archs in the cauldron tree are always
up-to-date :)
--
Olivier Blin - blino
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="002064.html">[Mageia-discuss] Mageia Mirror size
</A></li>
<LI>Next message: <A HREF="002067.html">[Mageia-discuss] Mageia Mirror size
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2074">[ date ]</a>
<a href="thread.html#2074">[ thread ]</a>
<a href="subject.html#2074">[ subject ]</a>
<a href="author.html#2074">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
mailing list</a><br>
</body></html>
|
