Michael G Schwern <[EMAIL PROTECTED]> writes:
>On Fri, Jul 26, 2002 at 08:19:26AM +0100, Nick Ing-Simmons wrote:
>> Makefile fragment below shows that vendor_install does
>> not do read/write of .packlist - why?
>
>Guess I forgot it when I added the vendor targets. Also, I don't seem to
>have a VENDORARCHEXP to use and I keep forgetting what the difference is
>between VENDORARCHEXP and INSTALLVENDORARCH. Why are the install targets
>reading from SITEARCHEXP and writing to INSTALLSITEARCH?
Originaly for AFS - where you write to one location and it apears at
another. Can also happen where (say) you write to /export/tools/...
but run from /opt/tools via a RO NFS mount. I can also imagine
writing to something that is to be a CDROM image, but reading from
a CDROM.
>
>Also, why is pure_perl_install checking in SITEARCHEXP for an old packlist
>and perl_site_install is checking in PERL_ARCHLIB. Are they checking each
>other? What should pure_vendor_install do then?
I think this is for the warning "installed elsewhere".
I assume this means that each should now check the other two.
>
>I also appears to have forgotten to fill out doc_vendor_install and
>uninstall_from_vendordirs.
>
>I guess if I don't have a $Config{vendorarchexp} available I should just
>generate it from $Config{installvendorarch}?
That will do for now - but presumably we should add vendor* to Configure
in same style as others.
--
Nick Ing-Simmons
http://www.ni-s.u-net.com/
