Am 31.10.2011 13:40, schrieb Philippe Reynes:
Hi all,
If you talk about this page :
http://www.mageia.org/wiki/doku.php?id=updates_policy&s[]=update&s[]=policy
<http://www.mageia.org/wiki/doku.php?id=updates_policy&s[]=update&s[]=policy>
I think that I'm the stupid guy. I don't really understand where is the issue
with
this page and e17.
I understand that e17 don't provide "stable" release with tarball. But I
never see
a "mageia forbid to package software without stable release".
And if yes, I mean, if it's what you want, how I can use E17 on mageia ?
(others than completly old and obsolete tarball).
To be honest, most E17 users i personally know use
something like http://omicron.homeip.net/projects/#easy_e17.sh
and compile and keep it up-to-date for themselves.
As all e packages provide SPEC templates for rpm builds,
maybe we could whip up some script which eases compilation
and installation of E17 packages, similar to nvidia-mgabuild.sh
for Nvidia drivers from Anssi.
Would be unsupported, but would provide a way for E17
users to have their preferred desktop and keep it
up-to-date as they wish?
regards,
trem
-------------------------------------------------------------------------------
*De :* Michael Scherer <[email protected]>
*À :* [email protected]
*Envoyé le :* Lundi 31 Octobre 2011 12h03
*Objet :* Re: [Mageia-dev] Re : E17 packaging
Le samedi 29 octobre 2011 à 18:38 +0100, Philippe Reynes a écrit :
> Hi all,
>
>
> Another solution is to package e17 twice (like chromium):
> - an E17 -stable based stable tarball, as it was almost/already done
> - an E17-unstable based on svn, as it's done now
I am a little bit stupid, but can you explain how it solve the issue of
not bypassing our update policy ?
--
Michael Scherer
