Linux - Software This 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. |
| 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
05-11-2011, 09:48 AM
|
#1
|
|
Member
Registered: Jul 2009
Posts: 33
Rep:
|
Perl installation in custom location
Hi,
I have an requirement of installing perl in custom location (NFS share that will be mounted on many machines).
e.g,
suppose '/usr/perly' is the NFS share, perl will be invoked as /usr/perly/bin/perl
I require all the libraries to be created on the same share so that no local libraries are referred. Also, I need hundreds of modules installed in the same location.
How do I do it with CPAN method?
I found this link useful, can you please suggest if this works.
http://www.popmartian.com/tipsntrick...-installation/
|
|
|
|
05-11-2011, 04:09 PM
|
#2
|
|
Senior Member
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 4,554
|
Probably the best source of information is to Google on Perl installation "as a non-root user."
When Perl is asked to look for a package, it walks down a list ('@INC') looking for it. When 'cpan' is used to install a package, it uses its "configuration" information to know where to put it.
Personally, what I would do here is to establish one "authoritative repository" of what the CPAN libraries should contain for all the various computers, and then, on each of them, I would 'rsync' the data to a local drive. Perl will make constant reference to the directories that are on its '@INC' list, and, quite frankly, I would not advise that they be NFS (Zzzz....) shares...
|
|
|
1 members found this post helpful.
|
05-12-2011, 09:48 AM
|
#3
|
|
Member
Registered: Jul 2009
Posts: 33
Original Poster
Rep:
|
Hi,
Thanks for reply,
I found below paragraph in 'perldocs'.. I could install newer perl in total different location without disturbing current perl versions.
Quote:
=head2 Maintaining completely separate versions
Many users prefer to keep all versions of perl in completely
separate directories. This guarantees that an update to one version
won't interfere with another version. (The defaults guarantee this for
libraries after 5.6.0, but not for executables. TODO?) One convenient
way to do this is by using a separate prefix for each version, such as
sh Configure -Dprefix=/opt/perl5.12.3
and adding /opt/perl5.12.3/bin to the shell PATH variable. Such users
may also wish to add a symbolic link /usr/local/bin/perl so that
scripts can still start with #!/usr/local/bin/perl.
Others might share a common directory for maintenance sub-versions
(e.g. 5.10 for all 5.10.x versions), but change directory with
each major version.
|
Though it has solved major problems for me, I still have some issues.
When I search for man pages for perl, it is showing pages meant for older perl version.
So situation is,
Quote:
#perl -v
This is perl 5, version 12, subversion 3 (v5.12.3) built for x86_64-linux
And Man pages are,
#man perl
The Perl motto is "Thereās more than one way to do it." Divining how many more is left as an exercise to the reader.
The three principal virtues of a programmer are Laziness, Impatience, and Hubris. See the Camel Book for why.
perl v5.8.8 2006-01-07 PERL(1)
|
How do I set manpath during compile time?
Is there a way I can copy man pages meant for NEWER perl version to location where OLD perl man pages are kept, without disturbing anything?
I cannot ask people to add new manpath to their profile file.
Please suggest on this.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 02:29 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|