in reply to Setting up a module's ownership in the makefile

I wouldn't reccomend doing that. It's bad manners to have a module installed in the standard installation directory with broken permissions. Any user would see the module is installed, but wouldn't be able to use it.

What if somebody else writes a module that uses yours as a prerequisite? His installations would be broken. If you really want to use a module privately, you could tell the user to specify a PREFIX, although that doesn't always work.

So I'd say it's almost assuredly a bad idea.

  • Comment on Re: Setting up a module's ownership in the makefile

Replies are listed 'Best First'.
Re^2: Setting up a module's ownership in the makefile
by tinita (Parson) on Aug 29, 2005 at 15:53 UTC
    you could tell the user to specify a PREFIX, although that doesn't always work
    i've read schwern's slides, but i always thought, perl Makefile.PL PREFIX=... LIB=... would work on all systems? so using 
    perl Makefile.PL PREFIX=~/perl LIB=~/perl

use lib "$ENV{HOME}/perl";

    [download]
    doesn't work on some systems? (i'm using that for cgipan, so it would be interesting to know where that doesn't work)

    oops, s/slices/slides/, thanks Happy-the-monk =)

[reply]
[d/l]
[select]
Re^2: Setting up a module's ownership in the makefile
by jacques (Priest) on Aug 25, 2005 at 22:41 UTC
    Any user would see the module is installed, but wouldn't be able to use it.

    But that's the point.

[reply]

      And what's preventing the user to install the module into his/her own directory? It's trivial if the module is Perl only and only slightly harder if it contains some compiled parts.

      Jenda
      XML sucks. Badly. SOAP on the other hand is the most powerfull vacuum pump ever invented.

[reply]
      A reply falls below the community's threshold of quality. You may see it by logging in.

In Section Seekers of Perl Wisdom