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
|
<!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=%3C20101129192504.GJ21938%40mars-attacks.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="001519.html">
<LINK REL="Next" HREF="001522.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Mirror layout, round two</H1>
<B>nicolas vigier</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C20101129192504.GJ21938%40mars-attacks.org%3E"
TITLE="[Mageia-dev] Mirror layout, round two">boklm at mars-attacks.org
</A><BR>
<I>Mon Nov 29 20:25:04 CET 2010</I>
<P><UL>
<LI>Previous message: <A HREF="001519.html">[Mageia-dev] Mirror layout, round two
</A></li>
<LI>Next message: <A HREF="001522.html">[Mageia-dev] Mirror layout, round two
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1520">[ date ]</a>
<a href="thread.html#1520">[ thread ]</a>
<a href="subject.html#1520">[ subject ]</a>
<a href="author.html#1520">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Mon, 29 Nov 2010, andre999 wrote:
><i>
</I>><i> The idea is not that the Mageia community would not support "extra"
</I>><i> packages.
</I>><i> It is just that if an "extra" package breaks, it shouldn't break a user's
</I>><i> system.
</I>><i> But if a "core" package breaks, we would expect that it would break many
</I>><i> users' systems.
</I>><i> Thus the priority to ensure that "core" packages are always fixed in a
</I>><i> timely manner.
</I>
I don't think we need repositories to define bug priorities. If a
package break the system, the bug report should mention it. And we can
also have minor bugs in "core" packages not breaking anything. Should
we fix them in a timely manner, before any critical bug on "extra"
packages breaking useful applications ?
>><i> - Some packages can have a different support time. On Mandriva, "Base
</I>>><i> system& components" was supported longer, but it was not clear which
</I>>><i> packages were part of this.
</I>>><i>
</I>><i> Core is proposed to be largely "base system & components". Part of the
</I>><i> idea is to make clearer, to everyone, which packages have an enhanced level
</I>><i> of support.
</I>><i> Support time is another (useful) question.
</I>
Why do we need two repositories for that ?
>><i> - Some packages have a lot of optional plugins, and we build them all,
</I>>><i> adding a lot of build requires. With main/contrib separation we need
</I>>><i> to add all the build dependencies to main, even if most of them are
</I>>><i> not runtime dependencies.
</I>>><i>
</I>><i>
</I>><i> We will have to be more selective for core packages, to avoid this problem.
</I>><i> Maybe "suggests", or other features being added with rpm5.
</I>
Suggests on BuildRequires does not exists. And we need them to be
installed for the build.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001519.html">[Mageia-dev] Mirror layout, round two
</A></li>
<LI>Next message: <A HREF="001522.html">[Mageia-dev] Mirror layout, round two
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1520">[ date ]</a>
<a href="thread.html#1520">[ thread ]</a>
<a href="subject.html#1520">[ subject ]</a>
<a href="author.html#1520">[ 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>
|
