Scribus 1.1.3 released. Ebuild attached. Note: SRC_URI has changed export WANT_AUTOCONF_2_5=1 export WANT_AUTOMAKE=1.6 Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 21423 [details] Tested scribus 1.1.3 ebuild.
Not sure why when you release 1.1.2 you removed the export WANT_*s but for CVS I need them. Other ebuilds have them, checked with rac re this. If it works without them, then I guess remove them. Please explain, if possible, when I'm emerging my own ebuild why I would need them, and when oneis officially released it might not?
Have been chatting to spyderous re the export WANT_*s. Maybe theres a difference in some file here. I definitely get a build failure without the exports. Anyway.. I guess take them out .. should be fine.
I notice the 1.1.2 ebuild has this: src_unpack() { unpack ${A} # Fix for python-2.3 compatibility (bug #32775) sed -e 's:#include "scribus.h":#include <Python.h>\n#include "scribus.h":g' \ -i scribus-1.1.2/scribus/plugins/scriptplugin/cmdvar.h } change the -i scribus-1.1.2/scribus/plugins/scriptplugin/cmdvar.h -i {$P}/scribus/plugins/scriptplugin/cmdvar.h
I mean, add the section to my ebuild, but change the -i scribus-1.1.2/scribus/plugins/scriptplugin/cmdvar.h to -i {$P}/scribus/plugins/scriptplugin/cmdvar.h
Heh, you notice? I believe I pointed that fix out. =P
Yes.. and you said you'd put it on the bug.. took ya time :) hehehehe.
Did I? It must've slipped my mind. I figured this was already in portage.
Nope. Just sync'd. Not there.
ebuild added. the autoconf/automake-stuff is not needed for release versions, because it already has it's configure/makefile.in-stuff. The python-fix is removed, because this has been integrated upstream.