Usage of configure during non-standard installation
I am a newbie when it comes to Linux but not completely lost :) I installed CentOS 7 a couple of weeks ago because this is what I have at uni. I have already managed to install a couple of applications, created a few custom icons in my Show Application but I am currently struggling to install GnuGP 2.1.12. Normally I would go for `yum install <app>` but this and a lot of other applications on CentOS 7 are outdated, e.g. git 1.8.x.
Installing GnuGP 2.1.21 (link) from sources requires to handle a bunch of dependencies which are also available on the same website. I guess if I used the default sequence below to each of the dependencies: Code:
./configre I have already read how to install application (here) but I would like to choose a custom folders for that, e.g. /opt. How should I proceed. Aforementioned dependencies will most likely be installed as libraries, include files etc. which GnuGP needs to function. I would like all of them to be installed in custom folders, somewhere away from system folders. Is it possible? If yes, would it be really hard to do? I have noticed ./configure accepts a lot of options, such as --prefix but I guess I need more than that, especially when it comes to locate custom libraries/extra files etc. Thanks. |
One suggested step by their documentation is that you should run autogen.sh:
Code:
./autogen.sh I don't understand your concerns about the /usr/bin, /usr/sbin tree, this is what it is there for. Installing the formal binaries for common applications. When you perform yvm install <app>, it usually places the executable images in any of: /bin, /sbin, /usr/bin, or /usr/sbin |
Quote:
I don't know how to check things like this and do any precautions in case things have gone wrong. I would probably have to reinstall the system. |
You can uninstall the new one and then re-install the former one using the yvm method. What you can do in the forward direction, you can do in the reverse direction.
|
as far as backing off and resetting to where it was before you ran the
Code:
./configure if by chance it was, then just re-install it the same way you did the first time. that should fix it. Where you are wanting to put everything you do using ./configure into /opt just to play it safe is a can do thing. then you're going to have to learn how to make your system look in there every time it is wanting to use something that usually goes into one of the bins or else where within the system which could get complected but it is still a possibility. with Slack or Void Linux one just makes a script then run it so that system then can take care of it. It knows where it is at if one wants to upgrade or remove same said item then simply use that 'custom' script to do so. Makes life using Linux/GNU a bit easier when installing outside of the repo. |
Are you sure I can install GnuGP using default options? I just want to point out that GPG2 in CentOS seems a special protected application because YUM somehow uses for its own purpose. I am still not convinced if I should do it!
BTW, thanks for your comments :) |
what is the worst case scenario if you install it and it does a ka pow on ya?
Are you able to recover from this worst case scenario? if yes, Then what was so bad about it that it stopped you from finding out first hand? |
Stop! Right now!
The point about enterprise-class distros is that they go for tried-and-tested rather than bleeding-edge. If Red Hat (and that's what your CentOS is) gives you a particular version of GnuPG, that is proof enough that the version in question is adequate. "Updating" can (and probably will) break things. If a program has a security fault, then Red Hat back-port the solution, incorporating the patch issued for the newer version into the one they use. On the general question of adding things to CentOS, read this http://wiki.centos.org/AdditionalResources/Repositories and this http://wiki.centos.org/PackageManagement/Yum/Priorities If you obey the rules, then you can install extra software safely; if you don't, then the only guarantee is that if it breaks you get to keep the pieces. |
Quote:
A "data part" system backup is a good idea. I also feel that one worst is that a few things need to be fixed, rather than the entire system be messed up to be unusable. |
Quote:
just gave him something to think about. He then needs to weigh out everything before making that decision. worst case then is re-install lessened learned. carry on smartly. |
If you want to experiment with other versions of software, the most-important consideration is your target. Do not allow the configure/make scripts to target the "usual" system-level directories. Do not invoke "root" privileges. Do not do anything that might require them. :tisk:
You should, instead, target a private directory that is intended for such purposes, such as /usr/local. Or, put it somewhere else altogether. The distro's packaging subsystem will be unaware (and, unconcerned) of its existence. It's a good idea to place it somewhere such that intended users of the package must add the location to their $PATH, e.g. by adding a statement to their .bash_profile. |
Hi,
I have installed GnuPG 2.1.12 and it works. Based on a script made by someone else, I have made the one below. Doing it manually would be very easy to make mistake, which I have probably made before :/ Now, everything has been installed and works ok. I have one only problem. I tried to verify signature files but I have got errors and I had to comment that block. Do you know why I have got errors? Thanks The code. Code:
#!/bin/bash |
All times are GMT -5. The time now is 08:14 PM. |