This is the mail archive of the
mailing list for the Cygwin project.
Re: libwin32-perl-0.191 (ready for upload and testing)
- From: Nicholas Wourms <nwourms at netscape dot net>
- To: rkitover at hotmail dot com
- Cc: "'Gerrit P. Haase'" <gp at familiehaase dot de>, cygwin-apps at sources dot redhat dot com
- Date: Tue, 30 Dec 2003 20:39:10 -0500
- Subject: Re: libwin32-perl-0.191 (ready for upload and testing)
- References: <Law9-OE43IQjOnfIOS30001a8a5@hotmail.com>
Thanks so much for testing my package! What a mess :)
Now that it seems we'll be providing perl module packages, I think we
should come up with some sort of naming standard for consistency. For
example, Red Hat prefixes their perl packages with "perl-" and generally
uses the same case as is found on CPAN. So if we were to adopt this
route, this package would be perl-libwin32-0.191-1.
Also, may I suggest we make a "release" subdir especially for perl
modules on the mirrors (like XFree86)? This way we can keep the perl
modules neatly tucked away in their own subdir hierarchy, rather then
cluttering up the already growing release TLD. Just a thought...
Some other food for thought:
1) Man pages are good, especially since they can be indexed and keyed.
Have builders use make manifypods prior to make install.
2) Try not to clobber the perllocal.pod, but rather come up with a way
to update it (perhaps regenerate it from a pool of fragments?).
3) Make a vendorinstalldir for Cygwin, to keep our mods separate from
user's local mods, but provide a stable api for dependencies like
mod-perl or what-not.