FS#4810 - Package gimp with python-fu suport

Attached to Project: Arch Linux
Opened by Javier Aravena (Phrodo_00) - Monday, 12 June 2006, 17:24 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 12 June 2006, 17:56 GMT
Task Type Feature Request
Category Packages: Current
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Would be great to have gimp with python suport as it's really cool to do scripts using them, and much better than script-fu, besides, archlinux already needs python so it doesn't requires lots of more dependences and also it only needs a --enable-python --with-pygimp added to the configure line.
This task depends upon

Closed by  Tobias Kieslich (tobias)
Saturday, 29 July 2006, 05:40 GMT
Reason for closing:  Implemented
Comment by Tobias Kieslich (tobias) - Monday, 12 June 2006, 19:57 GMT
the problem here is, that we need pygtk, which is NO! makedependency but a runtime requirement. PyGTK rests in extra and requires a whole bunch of package that are only available from extra. This is why it prolly won't make it to current and hence not to gimp. There seems no way to get only scripting support without the plugins interfaces that actually require pygtk.
Comment by Jan de Groot (JGC) - Monday, 12 June 2006, 20:48 GMT
python, libsvg-cairo, pycairo, libglade, libsvg, pygtk are the dependencies that it would pull in. These dependencies are not that spectacular or big, so we could consider moving them to current if we really need to.
Comment by Javier Aravena (Phrodo_00) - Monday, 12 June 2006, 20:58 GMT
what I think that could be done is to make it another package. Others distros such as debian or ubuntu provide the package gimp-python which contains python-fu. They build it from the gimp source but I don't know how they actually separate this plugin from the rest of gimp and still gimp works for them without requiring the dependences it creates. I think I'll ask the debian mantainer and try to make a pkgbuild. I'll submit the package to the aur if I manage to do it.
Comment by Jan de Groot (JGC) - Monday, 12 June 2006, 21:02 GMT
Debian just builds all and moves the plugins into a separate package. There's no dual-compile magic, they compile everything in one run and split the resulting packages.
Comment by Javier Aravena (Phrodo_00) - Monday, 12 June 2006, 21:15 GMT
alright... so... I'll check the diference between gimp with python and gimp without python and I'll erase everything that's gimp only so only the python part is there. tha bad thing is that it will require a huge download to install a minimum part of it, but if it gets added to extra someday that will solve it as it will be just one person downloading it.
I'll do it next thursday or something like that. I have to study chemestry right now (and math and more stuff later), thanks for your guidance Jan.
Comment by Tobias Kieslich (tobias) - Wednesday, 12 July 2006, 06:22 GMT
Jan, can you move in the extra packages to current if you like to maintain them there. Otherwise I just close that, because there is no other way to fix it.
Comment by Jan de Groot (JGC) - Wednesday, 12 July 2006, 06:30 GMT
It's pycairo, python-numeric and pygtk that have to be moved in that case. I don't see any drawbacks, the packages aren't that big, it adds about 2MB to current, which isn't that much.
Comment by Jan de Groot (JGC) - Thursday, 13 July 2006, 20:50 GMT
The move is done, python-numeric, pycairo, pygtk and pygobject are in current now.

Loading...