You are not logged in.
Pages: 1
Is there a script that can create new PKGBUILD using setup.py?
Offline
What do you mean exactly? If there is a setup.py file, you can just put this in the build function:
python setup.py install --prefix=/usr --root="$pkgdir" || return 1If you are asking something else, please clarify.
Last edited by tdy (2009-02-13 04:46:20)
Offline
I mean script that will generate new PKGBUILD. setup.py contains almost all information that is needed for PKGBUILD so why packager must write PKGBUILD by hands?
Offline
If someone has written a script for this, I don't know of it. Python PKGBUILDs are so simple to write that it doesn't seem worth the effort to create such a parser. You'd still have to manually fill in fields like (opt)depends, .install, source, md5sums, and possibly more depending on how much the author included in setup().
Last edited by tdy (2009-02-13 05:08:35)
Offline
What do you mean exactly? If there is a setup.py file, you can just put this in the build function:
python setup.py install --prefix=/usr --root="$pkgdir" || return 1If you are asking something else, please clarify.
I have a pkgbuild with a install.py file that ignores everything after "python install.py" and tries to write at /usr/local/bin and not at $pkgdir.
Is there any way to set the root= prefix for the entire pkgbuild? Or to set it before the python command?
Offline
If you don't want to dive into depth setup script the easiest solution is to call install under chroot and then move all files to $pkgdir
Offline
If you mean use chroot in the PKGBUILd, this will give permission error, as chroot cannot be used by non root users.
Offline
Pages: 1