Please find attached a simple live ebuild for scribus. Upstream says 1.3.4 is depreciated and 1.3.5 is not yet released. I think it's more reasonable to track SVN than to keep the 1.3.4 ebuild. See also: http://www.scribus.net/?q=node/145 The file format of 1.3.[45] is not yet finalized as those versions are intended for testing and preview only. I would not put it into unstable but keep KEYWORDS="". Rumors say the use of ** for unmasking is not yet widely known so I put a short note at the top of the ebuild ;)
Created attachment 164562 [details] scribus-9999.ebuild As promised above.
Ah, as you will see the ebuild is slotted. It installs to /opt/scribus/...
There's no point in live scm ebuilds, when upstream releases regularly.
You'd have a point if there weren't the obsolete 1.3.4 ebuild in the tree which is one and a half years old and depreciated by upstream. Everybody interested in testing a pre release version or looking for a grip in scribus development is much better served with the live ebuild. Everybody else using 1.3.4 will just shoot herself into the foot anyway. > There's no point in live scm ebuilds, when upstream releases regularly. How does scribus differ from gimp, wine in that regard? In case you reject this, I would at least remove keywords from 1.3.4.
(In reply to comment #4) > How does scribus differ from gimp, wine in that regard? These shouldn't be in the Gentoo repository either. (In reply to comment #4) > Everybody else using 1.3.4 will just shoot herself into the foot anyway. No. No one is supposed to use masked ebuilds. cc'ing maintainer for reference
>> Everybody else using 1.3.4 will just shoot herself into the foot anyway. > No. No one is supposed to use masked ebuilds. Dammit, I didn't realize 1.3.4 is already packagemasked. Sorry for the noise.
I have been using the hardmasked 1.3.4 version for a while, but I noticed that upstream has abandoned this branch. I tried your ebuild, and now I am running 1.3.5svn, and it works :) Thank you very much !