Skip Menu |
 

This queue is for tickets about the Module-Build CPAN distribution.

Report information
The Basics
Id: 21524
Status: rejected
Priority: 0/
Queue: Module-Build

People
Owner: Nobody in particular
Requestors: jonasbn [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Subject: wish: blacklist variants of PL_files and PM_files
Download (untitled) / with headers
text/plain 466b
I am using the features of PL_files and PM_files (whitelists) once in a while and this is nice for inclusion of special non-standard stuff. But it would be nice to have features supporting blacklists, so my suggestion is to implement: pm_files_blacklist pl_files_blacklist So a user of M::B can define a list of files, which should not be included by M::B while building the distribution. This could be modules/files used for testing, development etc. jonasbn
From: DROLSKY [...] cpan.org
Download (untitled) / with headers
text/plain 582b
On Sat Sep 16 05:14:26 2006, JONASBN wrote: Show quoted text
> I am using the features of PL_files and PM_files (whitelists) once in > a while and this is nice for > inclusion of special non-standard stuff. But it would be nice to have > features supporting > blacklists, so my suggestion is to implement: > > pm_files_blacklist > pl_files_blacklist > > So a user of M::B can define a list of files, which should not be > included by M::B while building > the distribution. > > This could be modules/files used for testing, development etc.
How is this different from using a MANIFEST.SKIP file?
Download (untitled) / with headers
text/plain 933b
On Sat Sep 16 11:07:32 2006, DROLSKY wrote: Show quoted text
> On Sat Sep 16 05:14:26 2006, JONASBN wrote:
> > I am using the features of PL_files and PM_files (whitelists) once in > > a while and this is nice for > > inclusion of special non-standard stuff. But it would be nice to have > > features supporting > > blacklists, so my suggestion is to implement: > > > > pm_files_blacklist > > pl_files_blacklist > > > > So a user of M::B can define a list of files, which should not be > > included by M::B while building > > the distribution. > > > > This could be modules/files used for testing, development etc.
> > How is this different from using a MANIFEST.SKIP file?
Hello, This would of course be a good solution and I cannot remember my original problem anymore. Please disregard this ticket for now, if I my need occurs again I will reopen the ticket, with a better description of my scenario. Sorry for wasting you time, jonasbn


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.