On Tue, 7 Aug 2007, Stuart Winter wrote:
Hiwhat did Stuart mean when he talks about the "at-style functions that glibc 2.5 is providing". I do know now, keep on reading :-)Sorry -I just saw your post on aosl -- glad you have worked out what I said :-)As for the tar issue, it is indeed an old one. Even Slackware's pkgtools package don't use the newer tar, they use "tar-1.13" instead which is, oddly enough, included in the tar-1.16-1-i486-1 package installed by Slackware 12 (I just checked it).Also Pat does not like the use of a modified makepkg -- he (and I) cannot see why it's necessary. This is one of the reasons he put checkinstall into Slackware to begin with -- he was having reports about broken (broken in what sense I don't remember), and part of this was due to the patched 'makepkg'. If you were to use Slackware's makepkg, he'd be happier -- I couldn't say whether he'd reinclude it again but it'd go some way to doing so.
Hi! :-)Pat and I discussed this a couple years ago. Checkinstall does use Slackware's native makepkg if it is running on Slackware. Check out the MAKEPKG and MAKEPKG_FLAGS in checkinstallrc (Note that the comments are somewhat outdated: makepkg IS the default):
# Location of the makepkg program. "makepak" is the default, and is # included with checkinstall. If you want to use Slackware's native "makepkg" # then set this to "makepkg" MAKEPKG=/sbin/makepkg # makepkg optional flags. These are recommended if running a newer Slackware # version: "-l y -c n" MAKEPKG_FLAGS="-l y -c n"As a side note, the reason for the existence of the modified makepkg is that back when I first wrote checkinstall the makepkg version included with Slackware didn't support command line options and there was no way to make it automatically search and script the symlinks and to not change permissions to root:root:755. So I patched it ;-)
Felipe.