diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/006027.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/006027.html | 147 |
1 files changed, 147 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/006027.html b/zarb-ml/mageia-dev/2011-June/006027.html new file mode 100644 index 000000000..138c8cc1a --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006027.html @@ -0,0 +1,147 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Update of backport, policy proposal + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Update%20of%20backport%2C%20policy%20proposal&In-Reply-To=%3CBANLkTi%3D%3DKrRid7yTZ_uEVtvC2zsqC59AnA%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006024.html"> + <LINK REL="Next" HREF="006031.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Update of backport, policy proposal</H1> + <B>atilla ontas</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Update%20of%20backport%2C%20policy%20proposal&In-Reply-To=%3CBANLkTi%3D%3DKrRid7yTZ_uEVtvC2zsqC59AnA%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Update of backport, policy proposal">tarakbumba at gmail.com + </A><BR> + <I>Sun Jun 26 10:58:04 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006024.html">[Mageia-dev] Update of backport, policy proposal +</A></li> + <LI>Next message: <A HREF="006031.html">[Mageia-dev] Update of backport, policy proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6027">[ date ]</a> + <a href="thread.html#6027">[ thread ]</a> + <a href="subject.html#6027">[ subject ]</a> + <a href="author.html#6027">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>2011/6/26 Wolfgang Bornath <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">molch.b at googlemail.com</A>>: +><i> A short reality check from userside: +</I>><i> +</I>><i> If foo-1.0 is in Mageia 1 and foo-1.1 is released upstream +</I>><i>  - foo-1.1 will likely be integrated in Cauldron very soon after +</I>><i>  - users will request to have foo-1.1 in Mageia 1 +</I>><i>  - if Mageia will not provide it then there will soon be local +</I>><i> repositories where local packagers will do a "backport" for their +</I>><i> friends. +</I>><i> +</I>><i> This may not be what Mageia backport policy will allow but we can not +</I>><i> avoid people doing and using this, no matter how many warning signs we +</I>><i> will publish. This has to be taken into account here. +</I>><i> +</I>><i> When a policy is found it has to be communicated very well, especially +</I>><i> if that policy means that the user can not have foo-1.1 in his stable +</I>><i> Mageia 1. +</I>><i> +</I>><i> This is important because former Mandriva users were used to get +</I>><i> almost all new versions backported, if not officially then in 3rd +</I>><i> party repos like MIB or MUD. +</I>><i> +</I>><i> -- +</I>><i> wobo +</I>><i> +</I>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. + +Look at Debian and Arch Linux who haven't any paid developers but +community distros. Stable Debian releases provide software from a +century ago for the sake of stability. Arch provides latest software +including core system and occaionally have breakages. I think Mageia +should be between two of them. Release latest software in updates for +non core system and libs, keep core system stable. Remove this +backports thingy. + +My 2 cents... +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006024.html">[Mageia-dev] Update of backport, policy proposal +</A></li> + <LI>Next message: <A HREF="006031.html">[Mageia-dev] Update of backport, policy proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6027">[ date ]</a> + <a href="thread.html#6027">[ thread ]</a> + <a href="subject.html#6027">[ subject ]</a> + <a href="author.html#6027">[ 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> |