On Fri, 2002-06-14 at 12:00, Guillaume Rousse wrote:
> > %defattr(444,root,root,755)
> Right, it's quite curious. Is there a reason for this ?

At the beginning, I had 644 perms too.  After looking at the perl base
installation, I noticed that almost all modules are installed with 444
perms, so I changed accordingly.

In a way, it makes sense.  Why having the write permission, when the
installed module is not meant to be modified?  If one needs to update a
module, most likely one would "rpm -U".

> > Perl can handle DOS style new lines.  Also many CPAN modules do contain
> > these.
> I know it does, as the module works :-)
> However, i think it is cleaner to have only one file encoding in the whole 
> distribution.

I concur.  However, this may have more to do with the CPAN module
sources.  IMHO, rpm is a packaging tool and one of its goal is to
maintain the source integrity.  Unless absolutely necessary, it should
not alter the source.  I am not sure line termination differences
warrant patches.  It's probably better left to the pagers and text
editors to do the right things.

> > Do you mean in the file list you have an entry for this directory, and
> > rpmlint should emit a warning for empty directories?
> The rpm contains the following files:
> [guillaume@silbermann guillaume]$ rpm -ql perl-XML-DBMS
> /usr/lib/perl5/site_perl/5.6.1/XML
> /usr/lib/perl5/site_perl/5.6.1/XML/XMLtoDBMS.pm
> /usr/lib/perl5/site_perl/5.6.1/i386-linux
> /usr/lib/perl5/site_perl/5.6.1/i386-linux/auto
> /usr/lib/perl5/site_perl/5.6.1/i386-linux/auto/XML
> /usr/lib/perl5/site_perl/5.6.1/i386-linux/auto/XML/XMLtoDBMS
> Actually, only XMLtoDBMS.pm is a real file, so the whole 
> /usr/lib/perl5/site_perl/5.6.1/i386-linux hierarchy is empty and useless.

Is the file list automatically generated, for example, by cpanflute,
using "find"?  In all cases, I concur that it will be helpful to get a
warning for empty directories.

BTW, it seems that some of my messages are not getting through to the
Cooker list, hmm... I wonder how to track this down.

Pete <[EMAIL PROTECTED]>




Reply via email to