How to Maintain Slackware with Applications that are Built Locally?
Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
How to Maintain Slackware with Applications that are Built Locally?
Hi,
When installing applications on Slackware that must be built locally because no *.tgz packages are available, is it better or even possible to somehow use makepkg to first build the application, then wrap it into a package, and then install the package with installpkg?
It would probably be very hard to do this especially when cmake is involved, but is this the recommended procedure? I use something called Wt-Toolkit which uses cmake to install, which usually doesn't work completely, then I do all kinds of special hacks to get a successful build, and by that time I have no idea about how to uninstall what I have done and upgrades become very hard.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
That depends. If you have source (say, a configure-make-make install), you could use src2pkg to create an installable/upgradeable Slackware package; you can download src2pkg from http://distro.ibiblio.org/amigolinux/download/src2pkg/.
You can (probably) find ready-to-build packages at SlackBuilds.org: slackbuilds.org.
You can create your own SlackBuilds; see how at SlackBuilds.org.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.