in reply to Re^2: Mac Perl Package Question
in thread Mac Perl Package Question

I'll back Tholosophy on this one -- don't mess with stuff in /System. You should do as CPAN does, and drop stuff in /Library/Perl. The big clue is that /Library is group writable:

[mildly:~] oneiros% ls -ald /System /System/Library /Library
drwxrwxr-x  41 root  admin  1394 Feb 17 08:01 /Library
drwxr-xr-x   4 root  wheel   136 Dec 15 19:12 /System
drwxr-xr-x  52 root  wheel  1768 Feb 19 09:45 /System/Library

[download]

This also goes for user-installed fonts, screen savers, pref panes, startup items, etc. -- put them in the appropriate directories in /Library not /System/Library

Replies are listed 'Best First'.
Re^4: Mac Perl Package Question
by Thilosophy (Curate) on Apr 12, 2005 at 03:51 UTC
    This also goes for user-installed fonts, screen savers, pref panes, startup items, etc. -- put them in the appropriate directories in /Library not /System/Library.

    For these things, you can even put them in ~/Library (that is inside of your home directory, for example /Users/YourName/Library). Most Mac applications will search there, too. Does not work for Perl modules, though (unless you manually adjust @INC, which of course is easy), and other users cannot see or use them (which in many cases is a good thing).

[reply]
Re^4: Mac Perl Package Question
by RobertJ (Acolyte) on Apr 12, 2005 at 14:45 UTC
    Thanks.

    Have another question. What exactly do these intall steps do?

    perl Makefile.PL
    make
    make test
    make install

    In the past I have checked a modules source and if it was pure perl I manually placed it in the correct directory. A week ago I had a module where this didn't work UNLESS I removed the comment statements; then, all was fine. I tried using the above steps but the "make test" wouldn't work. Someone on this forum sugessted skipping this because they suspected I didn't have something installed (I have perl that came with 10.2.x - think it's 2.6). The install "worked" but I still had to remove the comment statements?????
[reply]

      Really, they don't have to do anything, other than put the files in the correct place, in the case of a pure perl installation. However, it's possible that they're doing other things as well, as they may trigger other items to register that they now exist on your system. (XML::Parser comes to mind), or they may set up configuration information (like Bundle::libnet)

      For the most part, you can generally expect them to do the following (but remember -- these aren't necessarily rules, this is more like guidelines than anything else.)

      perl Makefile.PL
      Builds the file named 'Makefile' which is used by the make command. May derive values from the current perl installation, or prompt you for information, or expect you to pass in things through environmental variables or as command line arguments. It's somewhat common for this step to generate new files, or modify existing ones.
      make
      Compiles whatever components need it, and places them into the blib directory. (it's also possible that this step might generate new files, or modify existing ones).
      make test
      Runs a series of tests (typically in the 't' directory if it's a more recent module) to test that the module is working correctly on your system.
      make install
      Moves files to their proper location on your system.
[reply]
        Thanks. Very informative. For the particular module the only thing I could find that was "different" after the install was the addition of an empty directory

        "/Library/Perl/darwin/auto/File/Copy/Recursive"

        I have not been able to do a test with a t directory present. Someone on this forum suggested that I might be missing something in my install because I have Perl 5.6 that came with Mac OS 10.2.x. For the couple of module installs I have done I just skipped the step and everthing seems to work fine.
[reply]

In Section Seekers of Perl Wisdom