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/2011-June/006039.html | 134 +++++++++++++++++++++++++++++++ 1 file changed, 134 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-June/006039.html (limited to 'zarb-ml/mageia-dev/2011-June/006039.html') diff --git a/zarb-ml/mageia-dev/2011-June/006039.html b/zarb-ml/mageia-dev/2011-June/006039.html new file mode 100644 index 000000000..e5880192c --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006039.html @@ -0,0 +1,134 @@ + + + + [Mageia-dev] Update of backport, policy proposal + + + + + + + + + +

[Mageia-dev] Update of backport, policy proposal

+ Michael Scherer + misc at zarb.org +
+ Sun Jun 26 13:29:05 CEST 2011 +

+
+ +
Le dimanche 26 juin 2011 à 11:43 +0200, Daniel Kreuter a écrit :
+> On Sun, Jun 26, 2011 at 10:58 AM, atilla ontas <tarakbumba at gmail.com> wrote:
+> 
+> > Hi. I'm following this threat from the very beginning. While reading,
+> > i feel i'm reading a Mandriva Cooker mailing list posts. As a
+> > community distro, why Mageia developers still think like a Mandriva
+> > employee? Why backports and why so many policies, like a commercial
+> > enterprise distro? I mean, Mageia do not have paid developers to work
+> > on packages all the time. Also Mageia do not have so many packagers
+> > like Fedora or Ubuntu, So, why make so many things so hard?
+> >
+> > As wobo mentioned, people like latest and greatest software. I think,
+> > except a few users will use unofficial 3rd party repos to get latest
+> > software. While i was maintaining MVT (Mandriva Turkiye) repository,
+> > our users asked for GNOME 2.32 while Mandriva have GNOME 2.30 on
+> > official release.
+> >
+> > Personally i always hate the backports structure and policy. It
+> > confuses minds. Why Mageia need a backports repo, i really do not
+> > understand. Stability and bug free releases are of course a must. But
+> > it needs developers dedicated to work, almost paid developers. If a
+> > software do not related with core system, like vlc, it should included
+> > updates repo. Let upstream fix bugs and security issues. If a packager
+> > catchs a bug he should send a patch to upstream and wait for a new
+> > release. Otherwise, it is not packaging it is coding, which many
+> > potential packgers will avoid to contribute.
+> >
+> >
+> +1 I also see no usage of backports. I'm someone quite new to
+> Mandriva/Mageia so I wouldn't know what backports are for (Ubuntu has
+> nothing like this, Fedora too) so why backport?
+
+It was already explained why in another thread, and this was also
+answered in the various thread about mirror layout, on the Mandriva page
+about it on the wiki, on the mailling list at that time, and on various
+others documentation sources. 
+
+I really do not have the luxury to explain from scratch everything, so
+please look at the archive of the ml.
+
+And speaking of Ubuntu, there is :
+https://help.ubuntu.com/community/UbuntuBackports
+
+( or http://wiki.debian.org/Backports for Debian, or the proposal ( that
+stalled, as said in another thread ) for Fedora :
+https://fedorahosted.org/fesco/ticket/515 , due to
+http://fedoraproject.org/wiki/Stable_release_updates_vision )
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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