This sounds like a good solution to me, maybe use a dummy package to replace scribus-ng for now which depends on the scribus package.<br><br>-Sonic<br><br><div class="gmail_quote">On Thu, Feb 2, 2012 at 5:52 AM, ale rimoldi <span dir="ltr"><<a href="mailto:ale.comp_06@xox.ch">ale.comp_06@xox.ch</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hi devs<br>
hi malex<br>
<br>
for a long time, on debian (and some other systems, too) people have<br>
been using scribus-ng as the de facto stable version.<br>
<br>
now we need to plan a transition to get the "scribus" package to carry<br>
the new stable version and get the people to use it!<br>
<br>
currently, the situation has become rather complicated and there<br>
is imo a risk to see it become even more complicated,<br>
if we don't manage carefully the transition after the release of 1.4.<br>
<br>
<br>
but, let's first try to get the facts straight at least for debian (i<br>
expect the state for ubuntu to be similar to it):<br>
- stable carries 1.3.3.13 (from 2008!) as scribus and 1.3.5 (from<br>
december 2009) as scribus-ng<br>
- testing has 1.4rc3 as scribus (april 2011) and 1.4rc2 as scribus-ng<br>
- scribus' own repository contains 1.4.0 (january 2012) for<br>
the "scribus" package<br>
- scribus' own repository contains 1.4rc6 (january 2012) for<br>
the "scribus-ng" package<br>
<br>
on top of it:<br>
- for ubuntu there is a PPA with the current 1.5svn managed by the<br>
ubuntu project.<br>
- ubuntu users would prefer to have scribus' own packages being<br>
packaged as PPAs, too.<br>
- malex wishes to wait for the "armel" bug being fixed before pushing<br>
1.4 as a stable into the official debian repositories.<br>
<br>
<br>
now the big question: what do we want the people to use?<br>
<br>
in my eyes:<br>
- people should use 1.4.x for their daily work.<br>
- 1.5.0 is not ready yet to be used by people who are not involved in<br>
the development of scribus.<br>
<br>
<br>
despite of having been using debian and ubuntu for years now, i don't<br>
have deep knowledges of the packaging rules (so i'm not sure if my<br>
proposal is possible). but i'd like to suggest the following migration<br>
path:<br>
- the "scribus" package should carry 1.4.x on debian testing<br>
and on scribus' own repository. (i don't think anybody will come to a<br>
different proposal for this...)<br>
- scribus-ng should become a dummy package inviting the<br>
people to use the "scribus" package instead of "scribus-ng" (both in<br>
testing and in the scribus own repository). this could be achieved by<br>
putting in there a scribus 1.4 with a startup warning telling<br>
the users to switch to "scribus" (something like the ghostscript<br>
warning)<br>
- people using debian stable (or older ubuntus) will have to add the<br>
scribus own repositories to get 1.4 in the "scribus" package: we<br>
can't change the versions in the stable repositories.<br>
<br>
as soon as scribus 1.5 will be ready to be tested by a broader public<br>
(i think that the minimal requirement for it to happen, is to have<br>
the undo for text) it can be packaged as scribus-ng.<br>
<br>
<br>
by this proposal, i mainly want to avoid that users who are looking for<br>
a stable modern scribus are migrated to an unstable 1.5 without their<br>
express willing to do so.<br>
<br>
<br>
one last thought: i wonder if it's really useuful to have a scribus-ng<br>
package in the debian repositories... or if scribus-ng should in the<br>
future only be in the scribus' own repositories.<br>
scribus-ng was necessary, because 1.4 has taken so long to be<br>
released, but i'm really not sure, that it will be still useful if the<br>
releases get closer (as it has been proposed and -- i think --<br>
everybody wishes).<br>
if we can agree that scribus-ng should not be in the official debian<br>
repositories, i think that it should be possible to get apt to<br>
ask the users to replace scribus-ng by scribus making the transition<br>
much easier.<br>
as soon as scribus-ng will be needed again, it will be added<br>
again but only to the scribus' own repositories (this will be much<br>
easier to manage!)<br>
<br>
<br>
voilà the mail got longer than i would have liked...<br>
<br>
what are your thoughts?<br>
<br>
ciao<br>
a.l.e<br>
<br>
_______________________________________________<br>
scribus-dev mailing list<br>
<a href="mailto:scribus-dev@lists.scribus.net">scribus-dev@lists.scribus.net</a><br>
<a href="http://lists.scribus.net/mailman/listinfo/scribus-dev" target="_blank">http://lists.scribus.net/mailman/listinfo/scribus-dev</a><br>
</blockquote></div><br>