diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-October/009155.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-October/009155.html | 133 |
1 files changed, 133 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-October/009155.html b/zarb-ml/mageia-dev/2011-October/009155.html new file mode 100644 index 000000000..5085f2fc8 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-October/009155.html @@ -0,0 +1,133 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] E17 packaging + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20E17%20packaging&In-Reply-To=%3C1319728240.2146.45.camel%40localhost%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="009136.html"> + <LINK REL="Next" HREF="009158.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] E17 packaging</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20E17%20packaging&In-Reply-To=%3C1319728240.2146.45.camel%40localhost%3E" + TITLE="[Mageia-dev] E17 packaging">misc at zarb.org + </A><BR> + <I>Thu Oct 27 17:10:40 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="009136.html">[Mageia-dev] E17 packaging +</A></li> + <LI>Next message: <A HREF="009158.html">[Mageia-dev] E17 packaging +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9155">[ date ]</a> + <a href="thread.html#9155">[ thread ]</a> + <a href="subject.html#9155">[ subject ]</a> + <a href="author.html#9155">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le mercredi 26 octobre 2011 à 23:12 +0200, Florian Hubold a écrit : +><i> Am 26.10.2011 22:06, schrieb Michael Scherer: +</I>><i> > Le mercredi 26 octobre 2011 à 18:58 +0200, Florian Hubold a écrit : +</I>><i> > +</I>><i> >> If keeping old releases unchanged from distro to distro version is +</I>><i> >> your vision of improving quality and more satisfying for our end-users, +</I>><i> >> that's not my vision, sorry. +</I>><i> > Then we should simply remove e17 altogether. Because, by choice of the +</I>><i> > developpers, it is not stable enough to be packaged. +</I>><i> > +</I>><i> Yes, altogether that would be a logical conclusion, sadly but true. +</I>><i> Seems some maintainers can actually be worse than infamous 'nobody'. +</I>><i> +</I>><i> How to deal with that on the upgrade to mga2 in packaging terms, +</I>><i> display a message to E17 users to the extent of: +</I>><i> +</I>><i> "... e17 has been removed to improve on mageia overall quality, +</I>><i> please use another window manager / desktop environment ... " +</I>><i> +</I>><i> +</I>><i> And please: this is meant as a serious question following the +</I>><i> above conclusion ... +</I> +That's a good question but in fact, the situation is not really new. +That's already something we should do for any software dropped. + +Either we drop because something do not work anymore ( for example, +something unmaintained upstream, not rebuildable and no one able to fix +), or we drop because we replace. + +Replacing is seamless and we do it quite often, dropping is not. + +I would propose that we add a conflict on mageia-release, and make a +note in release notes. So on upgrade, package is removed, and people +have documentation. + + +Now, for the other problem of providing e17 without bypassing all our +update procedure, there is several possible solutions : + +1) We could move that to another repository, outside of Mageia, with +different rules until that's sutable to be integrated properly. 3rd +parties repos are bad IMHO, but if people do not want to follow the +policy for whatever reasons, that's unavoidable. + +2) We could find a way to not place some packages to stable release. +That would be quite complex, but doable. This way, people could use e17, +but only if they run cauldron. Thus, we are free of any +support/stability requirement. + +3) We could ship the stable part ( ie, those with a tarball like eina, +etc ) and provide a script to compile/install the missing part from +svn, since this would also free use from support/stability requirement, +and as a bonus, let anybody keep the newest version ( because again, I +doubt that e17 developpers are interested into getting old bug reports, +given past and current interactions ). Of course, we should warn people +upon installation that they are on their own, that their e17 will be +updated often ( for the same reason about developpers ) +. And of course, this assume that no updated tarball are needed for the +stable part. + +There is several way, and that's just the ones I can think in 5 minutes. + +But e17 is a package that we always drop sooner or later, and once in a +while, discovered again, and then dropped again. +-- +Michael Scherer + +</PRE> + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="009136.html">[Mageia-dev] E17 packaging +</A></li> + <LI>Next message: <A HREF="009158.html">[Mageia-dev] E17 packaging +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9155">[ date ]</a> + <a href="thread.html#9155">[ thread ]</a> + <a href="subject.html#9155">[ subject ]</a> + <a href="author.html#9155">[ 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> |