diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101014/001177.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101014/001177.html | 148 |
1 files changed, 148 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101014/001177.html b/zarb-ml/mageia-dev/20101014/001177.html new file mode 100644 index 000000000..12d28adee --- /dev/null +++ b/zarb-ml/mageia-dev/20101014/001177.html @@ -0,0 +1,148 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] How will be the realese cycle? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3CAANLkTikn1RM9SxzQUtdfPimJYmHrBu69RoBn9W_d9wys%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="001184.html"> + <LINK REL="Next" HREF="001178.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] How will be the realese cycle?</H1> + <B>Ahmad Samir</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3CAANLkTikn1RM9SxzQUtdfPimJYmHrBu69RoBn9W_d9wys%40mail.gmail.com%3E" + TITLE="[Mageia-dev] How will be the realese cycle?">ahmadsamir3891 at gmail.com + </A><BR> + <I>Thu Oct 14 16:00:50 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001184.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI>Next message: <A HREF="001178.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1177">[ date ]</a> + <a href="thread.html#1177">[ thread ]</a> + <a href="subject.html#1177">[ subject ]</a> + <a href="author.html#1177">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 14 October 2010 15:41, Tux99 <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">tux99-mga at uridium.org</A>> wrote: +><i> +</I>><i> +</I>><i> Quote: Buchan Milne wrote on Thu, 14 October 2010 15:27 +</I>><i> +</I>>><i> What aspects of the Mandriva backports solution are not satisfactory? +</I>>><i> +</I>>><i> -The fact that not everything is available as a backport? +</I>><i> +</I>><i> Yes, more packages should be available +</I>><i> (and as future packager I will do my part to make that happen) +</I> +Well, backporting a package is a one-liner, so it takes less than +minute to be done; that's not the issue. The issue is that a new +version of package A may need a new version or package B to work, so +package B needs to be backported too; and/or that the new version of A +doesn't work with older libs/kernels, so backporting isn't too much +time consuming for packagers, but making sure that that backport has a +good chance of working(tm) is the bigger burden/responsibility. + +I've seen, too many times, trigger-happy packagers backporting +packages that're not maintained by them (so they know it less than +those package maintainer(s)), breaking those packages and annoying the +maintainers of said packages. It's usually irresponsible to backport a +package without taking that package maintainer's opinion into account. +(an infamous example on that is gwibber being backported to 2010.1). + +><i> +</I>>><i> -That users don't know how to request a backport? +</I>><i> +</I>><i> It certainly could help publicizing backports and giving the user an easy +</I>><i> way to request specific packages +</I> +New users who frequented the forums always got to know what backports +are pretty fast. And bugzilla is the perfect system for asking for a +backport, that worked pretty good. + +[...] + +>><i> -That users aren't aware of backports? +</I>><i> +</I>><i> Yes, backports should be promoted better in drakrpm and in the web site. +</I>><i> +</I>>><i> -Something else? +</I>><i> +</I>><i> backports should be supported for security patches and bug fixes just like +</I>><i> the main packages (if not instead of the main packages). +</I>><i> Of course the security patch could be simply provided by backporting a +</I>><i> newer version of the package, no need to make patches for each version. +</I>><i> +</I> +That's they way backports has always worked, no specific patches, just +the latest cooker package pushed to backports "as is with no official +support", that's reasonable, packagers shouldn't promise to support +backports when they can't due to various reasons (time, effort.. etc). + +>><i> > The end users need to do less than now for to get new versions of +</I>>><i> > their +</I>>><i> > favourites applications. +</I>>><i> +</I>>><i> Less than 'urpmi --searchmedia Backports chromium' ? +</I>><i> +</I>><i> CLI is not ideal for 'normal' users. +</I>><i> +</I> +rpmdrake has a "Backports" filter that shows packages from backports +repos, that's easy to use even for new users. + +>><i> Or, should it be more obvious in rpmdrake or similar? +</I>><i> +</I>><i> I think they should be enabled by default, since it's my impression that +</I>><i> the majority of 'normal' users wants new versions of apps, those users who +</I>><i> DON'T want them can still always disable them. +</I>><i> +</I>><i> Backports shouldn't be second choice, it should be the default, since that +</I>><i> would make Mageia stand out from other distros as being the distro were +</I>><i> users get the latest versions of apps before any other major distro +</I>><i> provides them. +</I>><i> +</I> +Enabling them by default defies the purpose of having backports at +all; it's not for new users, it's more for slightly experienced users +or power users who want the latest versions of apps. + +-- +Ahmad Samir +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001184.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI>Next message: <A HREF="001178.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1177">[ date ]</a> + <a href="thread.html#1177">[ thread ]</a> + <a href="subject.html#1177">[ subject ]</a> + <a href="author.html#1177">[ 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> |