SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
after reading the changelog for slack 12 i notice that checkinstall has been classed as not working on slack12 (although it did on rc2) can someone recommend a replacement for that tool? i have the build scripts for near every other package i build from source but not all
How about creating SlackBuilds for the programs to install? Have a look at slackbuilds.org if a SlackBuild already exists, or simply create your own using the template..
think pat said in release about it not working with coreutils, although i made a few packages on RC2 and it seemed fine
Sat Jun 30 16:06:18 CDT 2007
extra/checkinstall/: This had to be removed because it does not work with the
latest coreutils. There is a readme in this directory with the URL to
checkinstall's homepage, so if you must use checkinstall poll the site
periodically to see if a version comes out that fixes this issue.
havent been able to get to the home page for checkinstall for a few days now so cant see if anything has been updated
I'm like others that wonder what is the safe beat with slackware-12 for a tgz-package tool.
Here's what I'm reading so please someone show me the light because it looks like slackware build scrips are our only options unless pat gets our checkinstall fixed for us all. I am still learning so checkinstall has been a good tool for me on slackware but I guess it's time to expand my knowledge and learn to make build scrips.
Checkinstall per pat:
Quote:
Due to an unfortunate incompatibility with the latest coreutils
that was not noticed until right before release, a working copy
of "checkinstall" was not available at the time of the Slackware
12.0 release. Stuart Winter was kind enough to upgrade
slacktrack (a similar tool) to work around the issue of
installwatch not working, but in order to do that every file on
the system has to be "touched" so that changed timestamps can be
used to find files that are new. Obviously, you will not want to
do that on a production system (but it is always best to have a
dedicated "build box" anyway).
A new and working checkinstall might also be availible by the
time you read this. The project's homepage is:
The functionality of slacktrack has been removed for
the release of Slackware 12.0.
This is because the 'installwatch' library does not handle
the new *at-style functions that coreutils-6.7 and greater
are using. This means that chown, chmod and friends from
coreutils-6.7 and greater will not work.
It is expected that installwatch will be updated shortly but
unfortunately not in time for the release of Slackware 12.0.
Options
-------
[1] Please consider using 'altertrack' -- an alternate version of
slacktrack (included within slacktrack package) -- but be aware
that this version will alter the contents of your filesystem.
Please see the 'FAQ'.
** Users of 'altertrack' are expected to build packages on
disposable development installations of Slackware only. **
[2] Downgrade to an older version of coreutils such as v5.97
and call the real slacktrack script:
/usr/bin/slacktrack-real
** Users of 'altertrack' are expected to build packages on
disposable development installations of Slackware only. **
So, once again I'm reading something that doesn't sound like something I would like to use.
Now, before everyone jumps on my case for sounding negative about this, I'm just trying to understand all these tools and if they are safe to use which looks like there are problems with all.
src2pkg seems to be working without problems on Slack-12. I'm not certain that the currently available release(1.3) still works, but I think so. The problems that checkinstall and slacktrack are having with installwatch don't affect src2pkg because I don't use the installwatch wrapper at all. I've just uploaded a new version(1.4) which I'm even more sure of.
I should mention that I'm still using the older version of the installwatch library since I uncovered a pretty serious bug in the new (0.7.0beta5) version -something not easily uncovered as most packages are unaffected. Hence, patches to checkinstall itself may not fix this.
I'm going a head with this release as it has been tested pretty well on Slack-11 and tested some with Slack-12. However, the next few days I'll be doing more testing with Slack-12, especially with BASH-3.2, which is still in the Slackware /testing directory.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.