On Sat, 28 Dec 2002, Ardo van Rangelrooij wrote: > Adam Heath ([EMAIL PROTECTED]) wrote: > > On Sat, 28 Dec 2002, Ardo van Rangelrooij wrote: > > > > > Well, then you better start filing bug reports against perl and the Perl Policy > > > (which I'm following by the letter, by the way). > > > > You aren't. > > Yes I am. Look at the rules files in all my perl packages.
You're module is both binary and perl. Perl policy doesn't document this. This is a bug in perl policy. It's very short sighted that the perl policy doesn't consider this. The obvious thing is to have the files split into separate dirs. > > > Please show me the section you're basing your bug reports on. > > > > Perl Policy 1.3 says vendor libraries are /usr/lib/perl5 and /usr/share/perl5. > > The very last line in the above section says: > > > > In each of the directory pairs above, the lib component is for binary > > (XS) modules, and share for architecture-independent (pure-perl) > > modules. > > > > Section 3 says packaged modules should use the vendor libraries. > > > > So, just going by perl policy, your package is non-compliant. > > Well, that depends on how you define a "module". To me it's the complete tarball > from e.g. CPAN. You apparently interpret it as a .pm file Well, honestly, I don't think in modules. I think in files. And, besides, there is *no* way your package could *ever* be compliant with perl policy. Your package is both XS and arch-indep. > > However, your package must *also* comply with debian policy. Which says that > > architectural independant files must be in /usr/share. It says this by saying > > package *must* follow the FHS, version 2.1, in section 10.1.1. > > Then the Perl Policy is not compliant with the Debian Policy. File a bug report. > Funny, the Perl Policy is a part of the 'debian-policy package'. Wouldn't be the first time something is not compliant with something else. debian-policy: /usr/share/doc/debian-policy/perl-policy.html So, what does debian-perl think? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
