You are not logged in.
I'm trying to create a PKGBUILD for my own Python program.
The source code has been packaged using Python's distutils. Now, AFAICT distutils do not help you in any intelligent way to include a man page, so I just used a MANIFEST template to add the file to the source package.
As for the PKGBUILD, I'm currently using an 'install -D -m0644' command (in the 'package' function) to copy the page from a directory under $srcdir to "${pkgdir}/usr/share/man/man1/${pkgname}.1.gz".
However, seeing that makepkg has some built-in functions for compressing man pages, I figured that maybe it could deal with the proper placement too? My manual approach works nicely, but well, I figure the less of a hack job, the better.
Thanks in advance - this is my first program and package build so I wanna get it right :)
Offline
Actually, installing it as you're doing it is the Right Thing. Good thought, though. And just for reference, here's a list of what makepkg does when it's building a package.
Offline
Thanks joyfulgirl - I guess I hadn't really thought through what kind of a deal makepkg is.
At any rate, I figured I wouldn't have been the only Pythonista dealing with this issue and starting reading other people's setup scripts and according to Mutagen's setup.py putting desktop software man pages in 'share/man/man1' under the 'installation prefix' (a local variable, usually '/usr' or '/usr/local') can be considered a POSIX universal. Don''t know if this is reliable or just one hack replacing another, but it would mean being able to let Python's setup script take care of pretty much everything.
Offline
putting desktop software man pages in 'share/man/man1' under the 'installation prefix' (a local variable, usually '/usr' or '/usr/local') can be considered a POSIX universal.
Yup, pretty much ubiquitous.
Don''t know if this is reliable or just one hack replacing another, but it would mean being able to let Python's setup script take care of pretty much everything.
Cool! Hope it works out.
Offline