Re: [rt.cpan.org #58445] overzealous usage of configure_requires considered harmful
On 2010-06-18, Jonathan Yu <email@example.com> wrote:
> On Fri, Jun 18, 2010 at 8:50 AM, Tina Mueller <firstname.lastname@example.org> wrote:
>> So. The svn repository of Module::Build contains the correct files
>> for building debian packages already.
>> But they are not in the CPAN package, and that was what I was asking for.
>> Could you just deliver those two files in the CPAN package?
> I am not sure if this would break our build of libmodule-build-perl,
> as having a debian/ directory in upstream tarballs tends to confuse
> our tools (which then think, and rightly so, that the package is a
> Debian native package instead of an upstream package we're
That's not how the native/non-native status is determined.
The issue with having a debian subdirectory in the upstream tarball is
that the debian subdirectory has traditionally been shipped in our source
packages in the form of a patch against the unpacked upstream tarball. So if
upstream tarball already has such a directory, the patch has to undo that,
which makes the patch larger and harder to read, and if the debian
subdirectory from upstream contains a binary file it can't be removed by a
With the new 3.0 (quilt) source format, any existing debian subdirectory
is removed during unpacking, so this isn't an issue if you use the new
I'm not following the context here, so I'm not sure if upstream shipping files
in a debian directory is a sensible thing to do (generally it isn't), but it
shouldn't cause any technical problems on the Debian side.