Here is a new ebuild for slackware pkgtools. It is required by checkinstall for creating slackware packages. Note that the upstream distribution is messed up, here's how I created the pkgtools-10.0.tar.bz2 tarball: mkdir pkgtools-10.0 cd pkgtools-10.0 wget ftp://slackware.mirrors.pair.com/slackware-10.0/source/a/pkgtools/_pkgtools.tar.gz wget ftp://slackware.mirrors.pair.com/slackware-10.0/source/a/pkgtools/*.8 tar zxf _pkgtools.tar.gz sbin/ mv sbin/* . rm _pkgtools.tar.gz makebootdisk rmdir sbin cd .. tar -cjf pkgtools-10.0.tar.bz2 pkgtools-10.0 Whenever a new slackware version is released, I assume it would be a good idea to recreate the tarball from the slackware mirrors with the same process. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 50462 [details] pkgtools-10.0.ebuild Note that the dependencies/LICENSE here were just guessed from looking at the scripts, I don't know how good they are.
jeff, just curious -- what's the purpose of having these in portage?
This is a dependency for checkinstall, which some people have voiced an interest for in order to create debian/slackware/rpm packages. See bug 4600 for that. It would also be good for the rare time when something isn't in portage and needs a manual from-source build, but the user still wants to use something like dpkg to keep a little control over it. Not something I would personally need to use, but as I recall it was an ebuild I wrote for a past bugday. -Jeff
Bug 4600 closed as WONTFIX; closing this one as well... Don't see any use for this otherwise.
