diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/006031.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/006031.html | 143 |
1 files changed, 143 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/006031.html b/zarb-ml/mageia-dev/2011-June/006031.html new file mode 100644 index 000000000..8d2df2fee --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006031.html @@ -0,0 +1,143 @@ +<!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=%3CBANLkTimRtMVLpxvrwGmHiho%3DcTzkcAZpDQ%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="006027.html"> + <LINK REL="Next" HREF="006034.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Update of backport, policy proposal</H1> + <B>Daniel Kreuter</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Update%20of%20backport%2C%20policy%20proposal&In-Reply-To=%3CBANLkTimRtMVLpxvrwGmHiho%3DcTzkcAZpDQ%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Update of backport, policy proposal">daniel.kreuter85 at googlemail.com + </A><BR> + <I>Sun Jun 26 11:43:12 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006027.html">[Mageia-dev] Update of backport, policy proposal +</A></li> + <LI>Next message: <A HREF="006034.html">[Mageia-dev] Update of backport, policy proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6031">[ date ]</a> + <a href="thread.html#6031">[ thread ]</a> + <a href="subject.html#6031">[ subject ]</a> + <a href="author.html#6031">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sun, Jun 26, 2011 at 10:58 AM, atilla ontas <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">tarakbumba at gmail.com</A>> wrote: + +><i> Hi. I'm following this threat from the very beginning. While reading, +</I>><i> i feel i'm reading a Mandriva Cooker mailing list posts. As a +</I>><i> community distro, why Mageia developers still think like a Mandriva +</I>><i> employee? Why backports and why so many policies, like a commercial +</I>><i> enterprise distro? I mean, Mageia do not have paid developers to work +</I>><i> on packages all the time. Also Mageia do not have so many packagers +</I>><i> like Fedora or Ubuntu, So, why make so many things so hard? +</I>><i> +</I>><i> As wobo mentioned, people like latest and greatest software. I think, +</I>><i> except a few users will use unofficial 3rd party repos to get latest +</I>><i> software. While i was maintaining MVT (Mandriva Turkiye) repository, +</I>><i> our users asked for GNOME 2.32 while Mandriva have GNOME 2.30 on +</I>><i> official release. +</I>><i> +</I>><i> Personally i always hate the backports structure and policy. It +</I>><i> confuses minds. Why Mageia need a backports repo, i really do not +</I>><i> understand. Stability and bug free releases are of course a must. But +</I>><i> it needs developers dedicated to work, almost paid developers. If a +</I>><i> software do not related with core system, like vlc, it should included +</I>><i> updates repo. Let upstream fix bugs and security issues. If a packager +</I>><i> catchs a bug he should send a patch to upstream and wait for a new +</I>><i> release. Otherwise, it is not packaging it is coding, which many +</I>><i> potential packgers will avoid to contribute. +</I>><i> +</I>><i> +</I>+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? + + +><i> Look at Debian and Arch Linux who haven't any paid developers but +</I>><i> community distros. Stable Debian releases provide software from a +</I>><i> century ago for the sake of stability. Arch provides latest software +</I>><i> including core system and occaionally have breakages. I think Mageia +</I>><i> should be between two of them. Release latest software in updates for +</I>><i> non core system and libs, keep core system stable. Remove this +</I>><i> backports thingy. +</I>><i> +</I>><i> My 2 cents... +</I>><i> +</I>This approach looks quite good, but the new software should be tested quite +good so the system will not break. Sure core system won't break with this +approach but what about the other software? + + +-- +Mit freundlichen Grüßen + +Greetings + +Daniel Kreuter +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: </pipermail/mageia-dev/attachments/20110626/d5eb4c0e/attachment-0001.html> +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006027.html">[Mageia-dev] Update of backport, policy proposal +</A></li> + <LI>Next message: <A HREF="006034.html">[Mageia-dev] Update of backport, policy proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6031">[ date ]</a> + <a href="thread.html#6031">[ thread ]</a> + <a href="subject.html#6031">[ subject ]</a> + <a href="author.html#6031">[ 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> |