[SOLVED] Compiling programs from source and dealing with dependencies on Slackware.
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.
I'm not sure what the warning is and I'm a bit worried about it.
It is just a warning that your man pages aren't compressed, thereby wasting a little bit of disk space. No real worry (but if you ever write a Slackbuild, you should go the extra mile and gzip your man pages).
Quote:
Originally Posted by Switch7
And for the symbolic links, I think I made the right choice and it was alright to remove the symbolic links correct?
It is just a warning that your man pages aren't compressed, thereby wasting a little bit of disk space. No real worry (but if you ever write a Slackbuild, you should go the extra mile and gzip your man pages).
You made the correct choice.
Thank you very much! Now that I overcame my biggest obstacle, slackware is defiantly going to be my main desktop distribution. I was still testing around to see if it was for me or not. Looks like I'll go subscribe to the Slackware CD/DVD now.
Switch7: You have ommited one important thing - in the name of slackware package, You should set info about arch, to which is the package designed.
The name of package should be made with this schema: packagename-version-arch-build.txz
Name and version can contain multiple "-" signs, but two last sections must be only alphanumeric signs without extra "-" signs.
Switch7: You have ommited one important thing - in the name of slackware package, You should set info about arch, to which is the package designed.
The name of package should be made with this schema: packagename-version-arch-build.txz
Name and version can contain multiple "-" signs, but two last sections must be only alphanumeric signs without extra "-" signs.
I seen different numbers in the build number. Instead of -1, I seen something like -29 (ex: libtorrent-0.12.5-x86_64-29.txz) but that's only when the package is a bundle and I wouldn't need anything other than -1 for normal packages?
This is not completely true. The name may contain dashes (the "-" characters) but the version must not have any dashes! So, if a source package has a version of "1.2.3-4" your package version must be changed to something like "1.2.3_4" - Slackware usually replaces dashes in a VERSION with underscores.
I seen different numbers in the build number. Instead of -1, I seen something like -29 (ex: libtorrent-0.12.5-x86_64-29.txz) but that's only when the package is a bundle and I wouldn't need anything other than -1 for normal packages?
This is not completely true. The name may contain dashes (the "-" characters) but the version must not have any dashes! So, if a source package has a version of "1.2.3-4" your package version must be changed to something like "1.2.3_4" - Slackware usually replaces dashes in a VERSION with underscores.
Thank you. I never had any idea this was supposed to be the official way it's used in slackware. I always thought slackbuilds was just third party packages. I'll defiantly take a look here.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Slackbuilds save time for future releases, and rebuilds.
