2008/1/15, Yaakov (Cygwin Ports) <[EMAIL PROTECTED]>: > Reini, > > For cygport, I made this elaborate postinstall procedure which appends > to perllocal.pod for each package as it is installed, based on what > Gentoo did way back when. Nevertheless, it's still of fairly limited > use, as it is restarted each time the perl core package is updated. > > AFAIK most distros, now including Gentoo, just remove the perllocal.pod > from DESTDIR and don't mess around with it anymore. > > So my questions to you are: > > 1) Does 5.10 still use perllocal.pod at all?
Yes, it does. > 2) If so, should we follow the lead of other distros, or maintain the > status quo? I don't have a strong opinion on this. It works okay (I added my vendor_perl modules from CORE, but not my two other vendor modules yet: Win32::GUI and libwin32), your perllocal.pod work is appreciated, and I believe we should keep it this way. I rather think I should switch from the gbs to cygport finally with my seperate perl modules. -- Reini ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Cygwin-ports-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cygwin-ports-general
