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.
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...)
As it has been already stated, makepkg offers to change permission of directories to 755 which is very common. Changing ownership to root:root may be handy too.
You probably missed at least another point. How do you convert symbolic links to shell script commands with tar ?
It's strange somebody couldn't understand features of such primitive tool like makepkg is
It's still best to check permissions by hand. For example, makepkg will not chown /bin to root:bin, which is what it should be. And i don't think it strips binaries either, or gzip man pages or anything like that that other package tools do.
All more work i have to do by hand myself.
Last edited by liquidtenmilion; 12-22-2005 at 10:59 AM.
It's still best to check permissions by hand. For example, makepkg will not chown /bin to root:bin, which is what it should be. And i don't think it strips binaries either, or gzip man pages or anything like that that other package tools do.
All more work i have to do by hand myself.
It's pointless to become angry so cool down, please
I get your points and know Arch's makepkg tool too. But it's rather a philosophical question about level of automation (stripping binaries, gzipping manual pages, removing documentation, etc.) Somebody would benefit of such features and somebody would refuse them and prefer more control. I find the level of automation of Slackware's makepkg balanced.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.