summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-June/005734.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005734.html')
-rw-r--r--zarb-ml/mageia-dev/2011-June/005734.html236
1 files changed, 236 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005734.html b/zarb-ml/mageia-dev/2011-June/005734.html
new file mode 100644
index 000000000..ff4129d5b
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-June/005734.html
@@ -0,0 +1,236 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Question about backports: calibre (bug 1659)
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Question%20about%20backports%3A%20calibre%20%28bug%201659%29&In-Reply-To=%3C4DF93238.5030904%40laposte.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="005644.html">
+ <LINK REL="Next" HREF="005737.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Question about backports: calibre (bug 1659)</H1>
+ <B>andre999</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Question%20about%20backports%3A%20calibre%20%28bug%201659%29&In-Reply-To=%3C4DF93238.5030904%40laposte.net%3E"
+ TITLE="[Mageia-dev] Question about backports: calibre (bug 1659)">andr55 at laposte.net
+ </A><BR>
+ <I>Thu Jun 16 00:29:12 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="005644.html">[Mageia-dev] Question about backports: calibre (bug 1659)
+</A></li>
+ <LI>Next message: <A HREF="005737.html">[Mageia-dev] Question about backports: calibre (bug 1659)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#5734">[ date ]</a>
+ <a href="thread.html#5734">[ thread ]</a>
+ <a href="subject.html#5734">[ subject ]</a>
+ <a href="author.html#5734">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Radu-Cristian FOTESCU a &#233;crit :
+&gt;<i>
+</I>&gt;&gt;<i> Release frequency never was a criteria for differentiating between
+</I>&gt;&gt;<i> pushing something to updates and something to backports.
+</I>&gt;<i>
+</I>&gt;<i> It should be. Otherwise, we should all be using OpenOffice.org 1.0.1. --
+</I>&gt;<i> security issues set aside.
+</I>&gt;<i>
+</I>&gt;&gt;<i> And I see no reason why it would be in favor of doing a bug fix update
+</I>&gt;&gt;<i> rather than a backport, especially if we ask to do a more stringent QA
+</I>&gt;&gt;<i> checking on updates, as it would put too much work on the team.
+</I>&gt;<i>
+</I>&gt;<i> Because Mageia (and Mandriva)'s vision of the concept of &quot;backports&quot; is not
+</I>&gt;<i> compatible with my common-sense.
+</I>&gt;<i>
+</I>&gt;<i> I have not used Mandriva very much in the past, because I hate the concept of
+</I>&gt;<i> &quot;backports&quot; -- yes, Ubuntu does them too, but Ubuntu backports are totally
+</I>&gt;<i> unsupported, so you can imagine their &quot;quality&quot;...
+</I>&gt;<i>
+</I>&gt;<i> I'd rather stick to &quot;updates&quot; -- this is also the reason I stopped using
+</I>&gt;<i> Debian, because the morons (yes, morons) were only pushing tzdata updates
+</I>&gt;<i> in &quot;volatile&quot;, not in &quot;updates&quot;, whereas ALL the other distro weres pushing
+</I>&gt;<i> tzdata updates in &quot;updates&quot;.
+</I>&gt;<i>
+</I>&gt;<i> If Mageia considers that a 6-7 months old package (for an application that
+</I>&gt;<i> released 32 times in the meantime) only deserves updates in &quot;backports&quot;,
+</I>&gt;<i> then I will probably stop reporting any possible bugs with this distro
+</I>&gt;<i> -- as a protest.
+</I>&gt;<i>
+</I>&gt;<i> It is indeed a matter of principle. I am personally using the latest
+</I>&gt;<i> calibre installed in /opt, not the official one, but again, it's a
+</I>&gt;<i> matter of principle.
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> Whatever is important and comes from upstream should go into updates IMHO.
+</I>&gt;<i> Backports, in my view, only make sense if they're coming from Release N+1
+</I>&gt;<i> *and* if they represent a major version bump -- such as FF4 over FF3.6, etc.
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> WRT calibre, Fedora has a simple way: it keeps a newer calibre packages in
+</I>&gt;<i> updates/testing for 1 week, and if no user complains about regressions, it
+</I>&gt;<i> goes into updates. This is because calibre is a &quot;leaf&quot; package -- no other
+</I>&gt;<i> package depends on it, so it only impacts those who are using it.
+</I>&gt;<i>
+</I>&gt;&gt;<i> Again, that's not a criteria. Every software is important to at least
+</I>&gt;&gt;<i> one person, and that would mean we should update everything if we start
+</I>&gt;&gt;<i> to update everything important to one group of users.
+</I>&gt;<i>
+</I>&gt;<i> I can see how important is calibre to Mageia users. Nobody noticed or cared
+</I>&gt;<i> that it is an antiquated version. They could have as well used notepad.exe
+</I>&gt;<i> from Win95.
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;&gt;<i> And for what it is worth, Fedora is discussing having separate update
+</I>&gt;&gt;<i> and backport ( <A HREF="https://fedorahosted.org/fesco/ticket/515">https://fedorahosted.org/fesco/ticket/515</A> ), even if the
+</I>&gt;&gt;<i> discussion seems to be going nowhere at the moment
+</I>&gt;<i>
+</I>&gt;<i> BS. I hope Fedora *never* uses backports!
+</I>&gt;<i>
+</I>&gt;<i> Their update policy is very clear *and* flexible:
+</I>&gt;<i> <A HREF="http://fedoraproject.org/wiki/Updates_Policy">http://fedoraproject.org/wiki/Updates_Policy</A>
+</I>&gt;<i>
+</I>&gt;<i> Please note these:
+</I>&gt;<i>
+</I>&gt;<i> &quot;Exceptions: Some classes of software will not fit in these guidelines.
+</I>&gt;<i> If your package does not fit in one of the classes below, but you think
+</I>&gt;<i> it should be allowed to update more rapidly . . .
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> Things that would make it more likely to grant a request:
+</I>&gt;<i> -- The package is a &quot;leaf&quot; node. Nothing depends on it or requires it.&quot;
+</I>&gt;<i>
+</I>&gt;<i> Calibre is a &quot;leaf&quot; package.
+</I>&gt;<i>
+</I>&gt;<i> If not, in the same document:
+</I>&gt;<i>
+</I>&gt;<i> &quot;All other updates must either:
+</I>&gt;<i> -- reach the criteria laid out in the previous section OR
+</I>&gt;<i> -- reach the positive Bodhi karma threshold specified by the updates submitter OR
+</I>&gt;<i> -- spend some minimum amount of time in updates-testing, currently one week.&quot;
+</I>&gt;<i>
+</I>&gt;<i> I am not sure why F15 stopped updating calibre to 0.8.0 in updates (Rawhide went
+</I>&gt;<i> up to 0.8.4, maybe 0.8.5 now), but for the versions up to and including 0.8.0,
+</I>&gt;<i> here's the dynamics of the updates:
+</I>&gt;<i>
+</I>...
+&gt;<i> Indeed, Mageia does not have the number of packagers that Fedora has.
+</I>&gt;<i> However, if Mageia's _policy_ is to rather have 6-7 months old versions in
+</I>&gt;<i> updates, I should probably realize that Mageia is not for me.
+</I>&gt;<i>
+</I>&gt;<i> No, I have not, and never will use any repository called &quot;backports&quot;. When a
+</I>&gt;<i> newer stable release of a distro is available, I should update to it if
+</I>&gt;<i> updates I need are not pushed into Release N-1 &quot;updates&quot; (even if that release
+</I>&gt;<i> is officially still supported with security patches), but again, &quot;backports&quot;
+</I>&gt;<i> as Mandriva and Mageia are seeing them -- i.e. backporting
+</I>&gt;<i> from Cooker/Cauldron, not from &quot;updates/testing&quot; nor from &quot;Release N+1&quot;
+</I>&gt;<i> -- does not fit my Zen.
+</I>&gt;<i>
+</I>&gt;<i> R-C
+</I>
+In my mind you make an excellent case for upgrading this application from upstream, and installing
+under /opt, as you say you do already.
+Which I do for Mozilla Seamonkey, for example, because of relatively frequent updates. (In that
+case I also apply some personal patches, but that is another question.)
+It is appropriate to report bugs for the application upstream. The fixes will trickle down to Mageia.
+Just because you use Mageia (or any other distro) doesn't mean you can't install 3rd party
+applications. Although certainly it is preferable that most are packaged in Mageia.
+
+Which brings up another point. Considering your concern for the application, maybe you would like
+to package it for Mageia. You could ensure that it is always up to date, and that it works
+properly, and is properly supported. (The packager is a key player in support.)
+Just because it is called a backport doesn't mean that it won't work.
+The packager mentoring program will help you get started :)
+
+--
+Andr&#233;
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="005644.html">[Mageia-dev] Question about backports: calibre (bug 1659)
+</A></li>
+ <LI>Next message: <A HREF="005737.html">[Mageia-dev] Question about backports: calibre (bug 1659)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#5734">[ date ]</a>
+ <a href="thread.html#5734">[ thread ]</a>
+ <a href="subject.html#5734">[ subject ]</a>
+ <a href="author.html#5734">[ 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>