Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

RFC: Perl Application installation locations

by blm (Hermit)
on Dec 20, 2005 at 06:18 UTC ( #517974=perlquestion: print w/replies, xml ) Need Help??

blm has asked for the wisdom of the Perl Monks concerning the following question:

If I was writing an application with perl where should I put the files? I know that for most apps it seems that

  • binaries in /bin
  • static data in /share
  • changing data in /var
  • library in /lib
  • config in /etc
  • When you install after initial install you might use a prefix of /usr/local instead of /usr
Now my app is written in perl. It has various modules not really of use to anyone except my app and some configuration files. The stickler is the perl modules. Should they be lumped in PERLINC with the more generally useful perl modules or somewhere else (eg /usr/share/appname)and use use lib qw(/usr/share/appname). To draw an analogy, Yum the rpm package utility has a script in /usr/bin and modules somewhere in /usr/share. I know yum is written in python so the analogy is of lessened value.

Can I get some thoughts on the matter?

Replies are listed 'Best First'.
Re: RFC: Perl Application installation locations
by tirwhan (Abbot) on Dec 20, 2005 at 09:31 UTC

    If you're looking to conform to some standard way of doing this you may want to look at the FHS, which contains all the detail you could ever want on the subject.

    Personally I'd say install your binaries in /usr/bin or /usr/local/bin, /bin is supposed to contain only essential binaries and should preferably not be cluttered by user applications (as a rule of thumb, /bin should contain only the binaries you need after a boot if you cannot mount anything except the root partition). perl isn't usually installed in /bin, and neither should your apps be.

    As for the libraries, I usuall install somewhere in @INC. If your app will only be installed on a range of machines which belong to your organisation, then you could install in a custom directory and use lib, but I think it's too much of a bother to keep track of which apps need which library paths and only use this method when I'm testing a newer version of the libraries with an older one still installed. Also, installing libraries all over the filesystem can make it hard for someone else to maintain the system because they have to check all your custom paths as well as the usual ones for outdated library versions.

    Another good thing to do is to convert your Perl tar.gz packages into the package format native to your platform( for example .rpm for Fedora) and install from there. This is trivially easy to do on .deb-based systems, due to the very useful dh-make-perl script, and I'd guess something similar is available for rpm as well (or you could always use dh-make-perl and then convert the resulting .deb into .rpm with alien). Sticking to the system packaging format makes it easier for an admin to know what version of what software is installed where, which application a particular file belongs to etc. It also simplifies installation and update for multiple machines.


    Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan
Re: RFC: Perl Application installation locations
by Happy-the-monk (Canon) on Dec 20, 2005 at 08:51 UTC

    It doesn't matter what your application is written in. C, Python, Perl, Bourne Shell or Intercal are just fine.

    In *NIX you consider what it is written for. Chose /opt or more often /usr/local as bases, if the application is simple, just drop it there. If it needs lots of executables or lots of data, create another subdirectory there. That's all. On other platforms, there are other habits.

    I'd expect others not to mix their modules with the system-wide Perl installation, unless they install directly from CPAN - or with the new perl's core =). But that's just my way of expecting it to be.

    Cheers, Sören

Re: RFC: Perl Application installation locations
by rinceWind (Monsignor) on Dec 20, 2005 at 10:04 UTC
    If I was writing an application with perl where should I put the files?

    I take it your Perl "application" is one or more Perl scripts, and a suite of modules. There are standard places where these go for installing as root (if you're not installing as root, this can be done - you set up your own custom directory tree with bin lib and man directories, and include lib and bin in PERL5LIB and PATH respectively).

    The default place to install will be the same directory tree as where perl itself is located, usually /usr/bin/perl or /usr/local/bin/perl. If you are using a standard install (by root) you won't need to know exactly where modules go under /usr/lib or /usr/share, as this is taken care of for you.

    Hope this helps

    --

    Oh Lord, wonít you burn me a Knoppix CD ?
    My friends all rate Windows, I must disagree.
    Your powers of persuasion will set them all free,
    So oh Lord, wonít you burn me a Knoppix CD ?
    (Missquoting Janis Joplin)

Re: RFC: Perl Application installation locations
by adrianh (Chancellor) on Dec 20, 2005 at 10:27 UTC
    Can I get some thoughts on the matter?

    If you're distributing Perl based applications PAR will be well worth looking at.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: perlquestion [id://517974]
Approved by neversaint
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others examining the Monastery: (2)
As of 2023-03-27 03:45 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Which type of climate do you prefer to live in?






    Results (63 votes). Check out past polls.

    Notices?