Update of /cvsroot/module-build/Module-Build/lib/Module
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv32199/lib/Module
Modified Files:
Build.pm
Log Message:
Add some extra text to the PREFIX stuff
Index: Build.pm
===================================================================
RCS file: /cvsroot/module-build/Module-Build/lib/Module/Build.pm,v
retrieving revision 1.183
retrieving revision 1.184
diff -u -d -r1.183 -r1.184
--- Build.pm 17 Jun 2005 04:27:14 -0000 1.183
+++ Build.pm 20 Jun 2005 18:11:09 -0000 1.184
@@ -741,11 +741,17 @@
Many systems have Perl configs that make little sense with PREFIX.
For example, OS X, where core modules go in
F</System/Library/Perl/...>, user-installed modules go in
-F</Library/Perl/...>, and man pages go in F</usr/share/man/...>.
+F</Library/Perl/...>, and man pages go in F</usr/share/man/...>. The PREFIX is thus set to F</>.
Install L<Foo::Bar> on OS X with C<PREFIX=/home/spurkis> and you get
things like F</home/spurkis/Library/Perl/5.8.1/Foo/Bar.pm> and
F</home/spurkis/usr/share/man/man3/Foo::Bar.3pm>. Not too pretty.
+The problem is not limited to Unix-like platforms, either - on Windows
+builds (e.g. ActiveState perl 5.8.0), we have user-installed modules
+going in F<C:\Perl\site\lib>, user-installed executables going in
+F<C:\Perl\bin>, and PREFIX=F<C:\Perl\site>. The prefix just doesn't
+apply neatly to the executables.
+
=item *
The PREFIX logic is too complicated and hard to predict for the user.
|
