diff options
author | Andy Dougherty <doughera@lafayette.edu> | 1999-04-19 12:27:07 -0400 |
---|---|---|
committer | Jarkko Hietaniemi <jhi@iki.fi> | 1999-04-20 08:50:54 +0000 |
commit | 67a4fa727c6f261b2e1417d3c6d0a2dfa11e3ebd (patch) | |
tree | 838d687c0df34e8e1dadc32c041039f6cdb53fe9 /Porting/pumpkin.pod | |
parent | af4c28eba723fbf00ea205abffcc1284501af686 (diff) | |
download | perl-67a4fa727c6f261b2e1417d3c6d0a2dfa11e3ebd.tar.gz |
Re: 5.006 Todo
To: The Perl Porters Mailing List <perl5-porters@perl.org>
Message-Id: <Pine.GSU.4.05.9904191623470.7838-100000@newton.phys>
p4raw-id: //depot/cfgperl@3264
Diffstat (limited to 'Porting/pumpkin.pod')
-rw-r--r-- | Porting/pumpkin.pod | 28 |
1 files changed, 23 insertions, 5 deletions
diff --git a/Porting/pumpkin.pod b/Porting/pumpkin.pod index c54c508158..8736a70994 100644 --- a/Porting/pumpkin.pod +++ b/Porting/pumpkin.pod @@ -1297,11 +1297,29 @@ Configure/build/install process still assume src='.'. If a vendor supplies perl, but wants to leave $siteperl and $sitearch for the local user to use, where should the vendor put vendor-supplied -modules (such as Tk.so?) If the vendor puts them in $archlib, then -they need to be updated each time the perl version is updated. -Perhaps we need a set of libries $vendorperl and $vendorarch that -track $apiversion (like the $sitexxx directories do) rather than -just $version (like the main perl directory). +modules (such as Tk.so)? If the vendor puts them in the default $archlib, +then they need to be updated each time the perl version is updated. +Perhaps we need a set of libries $vendorlib and $vendorarch that +track $apiversion (like the $sitexxx directories do) rather than just +$version (like the main perl directory). + +An alternative (and perhaps even better) plan might be for the vendor +to select non-default $privlib and $archlib directories, perhaps using +$apiversion instead of $version (or even just /usr/lib/perl5 with no +version stuff at all), and put modules into those directories (with perl +Makefile.PL INSTALLDIRS=perl). This would be fine unless the vendor +wanted to support different versions of perl installed at the same time. +(How many vendors *really* want to do that?) + +=item Separate directories for Perl-supplied and add-on man pages + +Man pages supplied with the perl distribution proper ought to go in +an appropriate man directory. Perhaps man pages supplied with add-on +modules ought to (at least optionally) go into a $siteman[1-9] directory. +For example, suppose that $privlib is /usr/lib/perl5 and $man1dir +is /usr/man/man1. Also, suppose $sitelib is /usr/local/lib/perl5. +In this situation, it might make sense for man pages to go into +/usr/local/lib/man/man1. =item Hint file fixes |