# Where should I place software I compile myself?

I require to compile some software on my Fedora equipment. Where's the most effective area to place it so not to hinder the packaged software?

0
2019-05-05 00:19:25
Source Share

If you desire your application to be readily available for all customers on the system and also you have the essential approvals, make use of/ decide. If you desire the application to be readily available just for you (and also origin), usage/ home/username

0
2019-05-08 12:16:23
Source

If there is opportunity - I would certainly recommend compiling your software program and afterwards developing FC plan (I think it's making use of yum to install software). After that you can install that plan of your very own assembled software program and also remove it without screwing up the entire system.

0
2019-05-08 08:53:31
Source

Most of the moment, I such as to position my very own assembled things in /opt. It's type of a pseudo - typical area. You can additionally take into consideration /usr/local, yet I favor to maintain my things 100% separated.

0
2019-05-08 08:40:01
Source

if you are compiling an application you can add its executables course in you PATH env variable. this will certainly not influence various other customers.

0
2019-05-08 08:35:02
Source

There's constantly the alternative to "place it where it belongs" yet write a straightforward rpm, first.

0
2019-05-08 07:10:46
Source

If you intend to able to conveniently install and also remove numerous applications you've constructed on your own, you can make use of Stow as a straightforward plan supervisor.

0
2019-05-08 06:50:21
Source

Two points I would certainly advise :

System vast : usage stow and also install under/ usr/local/stow/ plan - variation. After that you can conveniently switch over in between variation.

In my residence, or if I do not have/ usr/local write approvals, I directly install programs under ~/. neighborhood, which is hinted by XDG standard.

You can additionally make use of store in your area, although I never ever did :)

0
2019-05-08 06:49:48
Source

FHS says to put it in /usr/local where circulations should not be touching it. /usr/local/bin for the binaries /usr/local/src for the resource and also /usr/local/lib for collections. See the FHS spec for even more details

0
2019-05-08 06:39:01
Source

I have a little various arrangement than most individuals due to the fact that I do a great deal of growth. I have a/ home/jackson/bin/ directory that I install things right into and also I've modified my.bashrc including this :

export PATH=/home/jackson/bin/bin::$PATH export LD_LIBRARY_PATH=/home/jackson/bin/lib:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=/home/jackson/bin/lib/pkgconfig:$PKG_CONFIG_PATH  . I would not do this for every little thing, yet its wonderful throughout growth. 0 2019-05-08 06:33:19 Source Rule of thumb, at the very least on Debian - flavoured systems : • /usr/local for things which is "system - vast"-- i.e. /usr/local often tends to be in a distro's default $PATH, and also adheres to a typical UNIX directory site power structure with /usr/local/bin, /usr/local/lib, etc

• /opt for things you do not depend make system - vast, with per - application prefixes-- i.e. /opt/firefox-3.6.8, /opt/mono-2.6.7, and more. Things in below calls for even more mindful monitoring, yet is additionally much less most likely to damage your system-- and also is less complicated to remove given that you simply delete the folder and also it's gone.

0
2019-05-08 05:35:46
Source

Put them to /usr/local/src.

What I do is extract the resource in this directory site. It will certainly create a course like

/usr/local/src/postgresql-8.3.7

.

After that I create a symbolic link to it :

/usr/local/src # ln -s  postgresql-8.3.7 postgresql

.

Do all your structure in /usr/local/src/postgresql.

Doing points in this manner aids when you require to pop in between variations and also records what variation you are making use of.

0
2019-05-08 04:39:27
Source

If you actually do not desire it to conflict in all, do not place it throughout your $PATH. If you desire it in $PATH, at the very least see to it not to install to /usr/local. I've located that a great deal of software program looks there also if it's mounted by the distro right into /usr.

My favored means to install custom-compiled software program remains in my $HOME directory site. In this way you do not need to make use of sudo for anything, and also it's really perfectly divided from the remainder of your system. As an example : mkdir ~/stage ./configure --prefix=/home/username/stage && make && make install  . And also if you intend to, you can after that add /home/username/stage/bin to your $PATH.

0
2019-05-08 04:34:03
Source

This advises me, I require to make use of checkinstall regularly! In this way I simply do the common

 ./configure
make


 sudo checkinstall


to create a . deborah documents ...

0
2019-05-08 02:03:26
Source

Per the FHS, /usr/local/ is made use of for applications assembled from resource, while /opt/ is made use of for 3rd event applications not sustained by your os supplier.

0
2019-05-08 01:46:02
Source

It is in fact not that tough to create deborah's or rpm's from a resource tarball. In this way, you can make use of the centers of your distro's plan supervisor to maintain your system tidy. This is what I do, a lot of the moment : simply create a little rpm.

0
2019-05-08 01:34:50
Source