SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Not to mention, what are you supposed to do when upgrading a package from source, if you use checkinstall? Does anyone have a suggestion? I used to removepkg right before I called checkinstall to install the upgraded package. It seems to work, but seems ugly. Lately, if the software supports DESTDIR, then I use makepkg, then upgradepkg.
While it is what i use, you could very easily just use tar to create a package. Makepkg is essentially tar that can change permissions of files to 755 if you tell it to(not very helpful anyway, since most files aren't going to be 755...)
It wasn't like i was saying makepkg is bad, like i said, i personally use it. However, i hear it being praised here like it is the greatest thing since sliced bread. In reality it's no more than tar+chmoding to 755+symlinking, not very advanced. It doesn't compare with Arch's makepkg or gentoo's ebuilds.
In reality it's no more than tar+chmoding to 755+symlinking, not very advanced. It doesn't compare with Arch's makepkg or gentoo's ebuilds.
Yes, it doesn't compare. Thankfully. Being "advanced" is a very poor indicator of how effective, useful, and functional a particular system tool behaves. I continue to attest to how well it meets each of these criteria and would advocate anyone using it to create their Slack packages.