Bug #115081 for Module-Build: Include/Use content of .gitignore in additional to MANIFEST.SKIP

Sun Jun 05 06:15:22 2016 KES [...] cpan.org - Ticket created

Subject:

Include/Use content of .gitignore in additional to MANIFEST.SKIP

That will be handy to not include into MANIFEST files listed at .gitignore

Sun Jun 05 13:32:04 2016 ether [...] cpan.org - Correspondence added

On 2016-06-05 03:15:22, KES wrote: Show quoted text

> That will be handy to not include into MANIFEST files listed at .gitignore

I think this is a horrible idea. Files such as META.yml, which are commonly included in .gitignore, must be in MANIFEST.

Sun Jun 05 13:32:04 2016 The RT System itself - Status changed from 'new' to 'open'

Sun Jun 05 13:46:46 2016 LEONT [...] cpan.org - Correspondence added

Subject:	Re: [rt.cpan.org #115081] Include/Use content of .gitignore in additional to MANIFEST.SKIP
Date:	Sun, 5 Jun 2016 19:46:18 +0200
To:	bug-Module-Build [...] rt.cpan.org
From:	Leon Timmermans <leont [...] cpan.org>

On Sun, Jun 5, 2016 at 12:15 PM, Eugen Konkov via RT < bug-Module-Build@rt.cpan.org> wrote: Show quoted text

> That will be handy to not include into MANIFEST files listed at .gitignore >

I think that's making far too many assumptions about the author's workflow to be appropriate in baseline MB; it's generally easier for people to add this kind of behavior than for them to override it. Also, I'm not sure MB should make assumptions about the author using git (e.g. if it had made such assumptions when it was started, it would have built-in subversion or even CVS; who knows what we'll use in ten years). Leon

Sat Aug 06 16:20:41 2016 LEONT [...] cpan.org - Status changed from 'open' to 'rejected'