blob: bce5abdbe8f57ded815f5e1e1d8a5ba179b910f9 (
plain)
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
|
<br><br><div class="gmail_quote">On Mon, Oct 31, 2011 at 3:40 PM, Michael Scherer <span dir="ltr"><<a href="mailto:misc@zarb.org">misc@zarb.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Le lundi 31 octobre 2011 à 16:56 +0000, Philippe Reynes a écrit :<br>
<div class="im">><br>
> So, yes, there isn't any way to manage bug/security issue in a very<br>
> easy way when upstream team don't provide stable tarball. So, what is<br>
> the mageia policy in this case ? no packaging at all ? "private"<br>
> packaging ?<br>
<br>
</div>So far, there is no policy specific for this issue. Hence the importance<br>
of discussing.<br>
<br>
Personnaly, I think we should really try hard to avoid a 4th<br>
firefox-like problem.<br>
<br>
I also think the current way is not something that will satisfy upstream<br>
coders if we ship old versions of their software when they think it is<br>
not ready.<br>
<br>
So as Florian told, maybe packaging a proper script to update e17 could<br>
help. I think we can ship the stable bit of e17, for people wanting to<br>
use them.<br>
Or see<br>
<a href="https://www.mageia.org/pipermail/mageia-dev/2011-October/009155.html" target="_blank">https://www.mageia.org/pipermail/mageia-dev/2011-October/009155.html</a><br>
for other type of solution.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Michael Scherer<br>
<br>
</font></span></blockquote></div><br><br>Has there been any more discussion/progress on E17@mga? I have finally merged all the UnityLinux specs up with Mandriva.<br><br>We've always maintained a fuller suite of E17 pkgs and there are instructions to boot on how to do svn trunk checkouts and tarballing of the sources.<br>
<br>Anyone interested in doing a cross mdv<>mga maintainership of E17?<br><br>Regards,<br>Matt Dawkins<br>
|
