Yep.. finally done it :) Basically the same dependencies as 1.2.2.1 I think. Files are there now. It cannot really be slotted without being put into a different dir I dont think. We plan to version the lib names in 1.3.1cvs. It would be nice for Gentooers to have 1.2.2.1 and 1.3.0 installable at the same time though. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 63910 [details] copy of scribus-1.2.2.1.ebuild Working ebuild for 1.3.0 version of Scribus.
file 63910 works flawless overhere on x86 ...
Should work ok, you just wont be able to have 1.2.2.1 and 1.3.0 installed at the same time. Slotting would be better I think. 1.3.0 uses separate prefs files in ~/.scribus FYI so no conflicts on the user side.
simply copy scribus-1.2.2.1.ebuild to scribus-1.3.0.ebuild and make a ebuild scribus-1.3.0.ebuild digest regards, j
simply copy scribus-1.2.2.1.ebuild to scribus-1.3.0.ebuild and make a ebuild scribus-1.3.0.ebuild digest regards, jürgen
What's keeping you from putting this in the tree? It compiles and runs flawlessly here with a simple version bump of the old ebuild, tested on two different hosts. The new build discovers the previous installation's preference settings and migrates them to the new version when you first start it up. Works flawlessly in every respect.
working w/ a ebuild-copy of 1.2.2.1 for 4 weeks on x86 now ... and i still dont know why to slot this one ...
(In reply to comment #6) > working w/ a ebuild-copy of 1.2.2.1 for 4 weeks on x86 now ... and i still dont > know why to slot this one ... Me neither. Works on amd64 as well btw.
The point is we are still not saying 1.3.0 is stable enough for production press usage. For other stuff, yes, probably is. I went to press with my magazine last edition with 1.3.0cvs and it was fine, however, those that dont want surprises should probably still use 1.2.2.1. However, you might as well make 1.2.x arch and 1.3.x ~arch I guess. There shouldnt be any reason for compilation or installation issues for 1.3.x anyway. 1.2.3 and 1.3.1 coming soon too btw :)
and now 2 months working w/ 1.3.0 - can we have a ~arch plz?
FWIW, we are looking to release 1.3.1 within about a week... It'd be nice if that, when released, can get into ~arch.
1.3.1 is now done. New optional dependency: cairo 1.0 or higher. --enable-cairo is the configure option. Not really many benefits other than slightly better onscreen gradients and is possibly a little slower for now, replaces libart_lgpl if used. http://www.scribus.org.uk/downloads/1.3.1/scribus.1.3.1.tar.bz2 Release news in the morning.
http://www.scribus.org.uk/downloads/1.3.1/scribus-1.3.1.tar.bz2, even. same location as always so ebuilds should be ok..
It'd be nice for the PPC MacOS guys to pick this up too if possible, as Scribus can certainly run on OSX, however certain frameworks must be in place. If those guys can have a read of http://aqua.scribus.net and see what we may need to do if there are any changes required in base CVS to support them. FWIW, it should also run on most if not all of the platforms Gentoo actively supports and it'd be nice to push it across there too.
What about the sloted ebuilds Craig talked about earlier? Does Scribus 1.3.1 have "support" for it. Would be great to have 1.2.x and 1.3.x installed side by side since 1.3.x is not yet production ready (Or has this changed, Craig - e.g. is the new file format ironed out?).
Scribus doesnt "support" slots, however, it would have to be --prefix'ed into a different directory as 1.2.x, and that will work. I have about 10 different versions installed here myself. The preferences files are already separated and 1.3.x offers to migrate 1.2.x preferences for the user (uses a completely different file). The new file format is not ironed out, and will be phased in over time, with major work starting now in 1.3.2cvs. I would actually say people can use 1.3.x or cvs, I do, and its really quite good, and miles better than 1.2.x. When we release, we plan stability for that release, so even if the file format is in flux during the time before a release, once released it should be fine.
No movement yet here? Need help anywhere?
what about the cairo-support?
How do you mean? 1.3.1 doesnt need it, and Gentoo doesnt have to have the option to enable it. Support for it could be added once cairo 1.x goes stable. The cairo issue should not hold up 1.3.1 going into portage though.
Is there a 1.3.x ebuild in the works or will there be no ebuild in the near future?
Hanno?
Added as masked package, supports cairo-useflag. To install, add app-office/scribus to /etc/portage/package.unmask and also x11-libs/cairo if you want cairo-support (this can and will break other things!).
Thanks :) Emerges ok.
Thanks hanno, the ebuild works. Great work ones again from the Scribus volks! Hanno, could you please give a short statement whether or not the ebuild will be transformed to a sloted ebuild (to keep a stable 1.2.x release of Scribus next to it) in the next time? If not, maybe you can give us your reasons (so that e.g. somebody else can do it if you just don't have enough time). I'm only asking that to avoid duplicated work. Thanks in advance.
If there's a trivial way to slot the ebuild, I can do it. Maybe craig wants to comment on that.
I'm not entirely sure what you need to slot the ebuild in terms of building Scribus. It will happily accept a --prefix argument in configure, but the libs are not named by version so they cannot exist in the same directory. If this is the requirement so a prefix is not used, then maybe we can slot 1.3.2 if I push versioned lib names up the priority list (if thats what is required). Let me know.
