From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20101129/001511.html | 97 +++++++++++++++++++++++++++++++++ 1 file changed, 97 insertions(+) create mode 100644 zarb-ml/mageia-dev/20101129/001511.html (limited to 'zarb-ml/mageia-dev/20101129/001511.html') diff --git a/zarb-ml/mageia-dev/20101129/001511.html b/zarb-ml/mageia-dev/20101129/001511.html new file mode 100644 index 000000000..ea696959b --- /dev/null +++ b/zarb-ml/mageia-dev/20101129/001511.html @@ -0,0 +1,97 @@ + + + + [Mageia-dev] Mirror layout, round two + + + + + + + + + +

[Mageia-dev] Mirror layout, round two

+ Samuel Verschelde + stormi at laposte.net +
+ Mon Nov 29 17:08:54 CET 2010 +

+
+ +
+Le lundi 29 novembre 2010 17:02:36, nicolas vigier a écrit :
+> 
+> On Mon, 29 Nov 2010, Samuel Verschelde wrote:
+> 
+> > 
+> > Indeed, however it helps showing that there's a set of packages which is supported, and another one which is only on behalf of the maintainer. In a community driven distribution, this distinction may remains valid : some packages are officially supported by the distribution, others may or may not be, depending on the maintainer (or lack of maintainer).
+> 
+> We don't need separate medias to show that there are two sets of
+> packages, supported and unsupported. I think using separate medias adds
+> useless complexity. We could for instance provide a file on api.mageia.org
+> containing the list of officially supported packages. It would also have
+> other advantages :
+>  - You can see how many unsupported packages and which ones are installed
+>    on your system. This is not possible with main/contrib, if you enabled
+>    contrib temporarly to install a few packages.
+>  - You can change the package status (supported/unsupported) after the
+>    release, if needed.
+>  - Some packages can have a different support time. On Mandriva, "Base
+>    system & components" was supported longer, but it was not clear which
+>    packages were part of this.
+>  - This file could also list known security issues for unsupported
+>    and supported packages.
+>  - Some packages have a lot of optional plugins, and we build them all,
+>    adding a lot of build requires. With main/contrib separation we need
+>    to add all the build dependencies to main, even if most of them are
+>    not runtime dependencies.
+> 
+
+Indeed maintaining the list of supported packages outside the repository is an interesting approach (better yet that misc's tag based proposal, I think).
+
+Regards
+
+Samuel Verschelde
+
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1