Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I run Slackware and have been installing from source using checkinstall since I got this computer. My /usr/local/src directory was filling up fast, so I recently deleted everything there to free up space. Later I was hunting around in packages and saw that checkinstall creates two .tgz files in the source directory of whatever it's installing. The first looks like the actual package that in installs, so I don't see why there's any harm in deleting that (you can always redownload and make), but each one also has a backup-foo.tgz. I looked around at some documentation but don't understand exactly what this backup package is. Is it wise to keep these for everything I install, and, if there is a good reason to do this, is there a way to automatically put all these backup packages somewhere else (so I can continue deleting source directories to save space)?
Ok, I've read the file and set up a packages directory, but will the backup packages go there too? What exactly are the backup packages, and should I care about them? Also, I assume you are deleting the .tar.gz and untarred directory manually after installing each package?
Originally posted by jrdioko
Ok, I've read the file and set up a packages directory, but will the backup packages go there too? What exactly are the backup packages, and should I care about them?
I don't know anything about any backup packages.
Also, I assume you are deleting the .tar.gz and untarred directory manually after installing each package?
I usually keep the source on my server in /downloads just in case, along with the Slackpacks I create in /tarballs
I do read in the documentation
Additionally, it will leave a copy of the package in the source directory,
the package's name will be name-version-architecture-release.tgz.
but I don't remember it doing that with my present setup. I believe that is the default if you don't specify a path for the tarball. I'll post my file here on pastebin.com so you can look at it. They delete entries after a period of time, so if you miss it, let me know.
I read that, but, if I'm not mistaken, those backup packages seem to be created for every package I install, even if I'm not overwriting anything I'm aware of. I'd also like to know how important they are (what are the chances of a make install overwriting something important anyway?), and if they get put in the packages directory specificed in the checkinstallrc file.
Checkinstall only does what 'make install' or similar calls for. So, it won't protect you from a script which wipes out previous config files. As far as I know, PAK_DIR is the location for newly created packages, not old files.
Well, I understand that I won't be protected from some malicious/poorly-designed program that does something like wiping out config files, but shouldn't I be safe with the vast majority of things after, say, running the program once to make sure all is well? I can manually move these backup packages to the PAK_DIR if necessary, but I'd like to know why they're created with every installation (even when things aren't being overwritten) and if I'm missing anything before I go deleting them every time.
Meaning the second time it's ever run or the second time it's run for a particular package name? In either case, why would it do so if you've already removed (or don't have in the first place) any previous versions of the program?