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.
Yea, the uncompressed man pages is another one I didn't list. You'll also find alot of /usr/share/{doc,man} directories in checkinstall packages too. I've noticed that sometimes an install will choke on a man symlink. That or it just overwrites it with a regular directory. Then you have 2 seperate man directories... You also don't have gzipped info pages and the 'dir' info file gets written everytime. Binaries and libraries don't get stripped as well...
Originally posted by jong357 Well, I stay away from checkinstall not because of personal prefrence, but because it absolutlely does NOT work in the slightest, as I have already stated. But yea, if you find something easy and enjoyable to use because it's automated then checkinstall fits that bill quite nicely. Again... IF it works in the first place....
Evidently, if Pat includes it in Slackware (it's prolly in /testing or /extras), it gets his blessing. He may have some misgivings for using it himself, but since he includes it in the distro, it must have some merits.
I'm not such a purist that I'm going to want to build each and every package that I make by hand. For personal use, Checkinstall is fine, IMO. I don't want to know the ins and outs of building them...I just want to be able to quickly build them when I feel I need a package created.
The one on linuxpackages wasn't too bad, although it left some things to the imagination (like the whole install directory) guess it's time to use explodepkg and the source tree.
Thanks for all this information guys. From what I'm reading I think I might try the harder way without checkinstall. I'll see how that goes.
Sorry for the late reply. I've been getting really busy lately. Soccer has just started so two days out of the week is gone. Not to mention exams are just two weeks away so teachers are starting to pile last minute assignments .
I'm hoping to try this Friday right after school as Saturday and Sunday are booked for school work .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.