Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Since I've been running Suse, I've been simply downloading packages in my home folder and gunzipping & tarring them there. Then within the folder created in my home, I would run my ./configure && make && make install.
Is this considered sloppy?
Should I install the packages in another location?
Should I have more options when ./configure, make & make install?
Distribution: Ubuntu, Debian, Various using VMWare
Posts: 2,088
Rep:
For Suse, the most common way of installing packages is to use Yast, the package manager.
I always prefer to stick to packages for my distro rather than compiling from source, as it keeps everything consistent. For example, if you compile foo from source then it won't be seen by your distro's package manager. If you then try installing bar with your package manager, and bar depends on foo, then it won't know that foo is actually installed.
It is not "sloppy" to compile from source, you can get more optimised programs that way, but it is generally easier to use your distros package manager.
I would run my ./configure && make && make install.
Is this considered sloppy?
Yes.
Quote:
From fueldistributa
Should I install the packages in another location?
Yes, typically /usr.
Quote:
From fueldistributa
Should I have more options when ./configure, make & make install?
What methods should I practice?
It is best to not use make install at all or to otherwise manually install software on your system, and to use a package manager instead. The reason is that you want to be able to cleanly remove whatever software you installed if you ever need to. In the case of your SuSE, I believe the package manager is Yast (but I'm not sure). In the case of my Mandrake 9.0, the package manager is RPM. If you run across software that simply isn't in the package format that your package manager supports, you want to build that software into a package for your package manager and you want to do that while running as a regular user (i.e. not as root). Then you can use your package manager to install and remove that software at will. Converting unpackaged software into packaged software doesn't look to be all that difficult but I have found documentation concerning the exact specifics on how to do it to be very lacking, so expect to be doing a lot of trial and error but consider the result to be well worth it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.