zarb-ml/mageia-dev/2011-October/009258.html


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Re :  Re :  Re :  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%20Re%20%3A%20%20Re%20%3A%20%20Re%20%3A%20%20E17%20packaging&In-Reply-To=%3C1320097202.2218.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="009241.html">
   <LINK REL="Next"  HREF="009051.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Re :  Re :  Re :  E17 packaging</H1>
    <B>Michael Scherer</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Re%20%3A%20%20Re%20%3A%20%20Re%20%3A%20%20E17%20packaging&In-Reply-To=%3C1320097202.2218.45.camel%40localhost%3E"
       TITLE="[Mageia-dev] Re :  Re :  Re :  E17 packaging">misc at zarb.org
       </A><BR>
    <I>Mon Oct 31 22:40:02 CET 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="009241.html">[Mageia-dev] Re :  Re :  Re :  E17 packaging
</A></li>
        <LI>Next message: <A HREF="009051.html">[Mageia-dev] udev in initrd and/or using dracut (LVM root fs	related)
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#9258">[ date ]</a>
              <a href="thread.html#9258">[ thread ]</a>
              <a href="subject.html#9258">[ subject ]</a>
              <a href="author.html#9258">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Le lundi 31 octobre 2011 &#224; 16:56 +0000, Philippe Reynes a &#233;crit :
&gt;<i> 
</I>&gt;<i> So, yes, there isn't any way to manage bug/security issue in a very
</I>&gt;<i> easy way when upstream team don't provide stable tarball. So, what is
</I>&gt;<i> the mageia policy in this case ? no packaging at all ? &quot;private&quot;
</I>&gt;<i> packaging ?
</I>
So far, there is no policy specific for this issue. Hence the importance
of discussing. 

Personnaly, I think we should really try hard to avoid a 4th
firefox-like problem.

I also think the current way is not something that will satisfy upstream
coders if we ship old versions of their software when they think it is
not ready. 

So as Florian told, maybe packaging a proper script to update e17 could
help. I think we can ship the stable bit of e17, for people wanting to
use them. 
Or see
<A HREF="https://www.mageia.org/pipermail/mageia-dev/2011-October/009155.html">https://www.mageia.org/pipermail/mageia-dev/2011-October/009155.html</A>
for other type of solution.

-- 
Michael Scherer

</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="009241.html">[Mageia-dev] Re :  Re :  Re :  E17 packaging
</A></li>
	<LI>Next message: <A HREF="009051.html">[Mageia-dev] udev in initrd and/or using dracut (LVM root fs	related)
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#9258">[ date ]</a>
              <a href="thread.html#9258">[ thread ]</a>
              <a href="subject.html#9258">[ subject ]</a>
              <a href="author.html#9258">[ 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>