develooper Front page | perl.perl5.porters | Postings from February 2022

Re: What should go in dist/ and cpan/

Thread Previous | Thread Next
From:
Leon Timmermans
Date:
February 24, 2022 02:58
Subject:
Re: What should go in dist/ and cpan/
Message ID:
CAHhgV8itLfXMXT1RjRO5TufXNxNGb-o4=-psScX1H6PnFbnwZA@mail.gmail.com
On Thu, Feb 24, 2022 at 2:23 AM demerphq <demerphq@gmail.com> wrote:

> On Fri, 24 Dec 2021, 15:57 Nicholas Clark, <nick@ccl4.org> wrote:.
>
>> Note, there is no reason to stick to just 3 subdirectories ext/ dist/ and
>> cpan/
>>
>> We could split dist and go 4 ways:
>>
>> ext:
>>      unchanged. core-only
>>
>> bundle:
>>     what was cpan/
>>
>> dist:
>>     upstream blead, dual life
>>
>> cpan:
>>     blead can patch if needed
>>
>>
>>
>> I think that this layout would address both concerns
>>
>
> One thing I find annoying is having to remember which one a given module
> is in. Could we maybe add another that is a symlink directory into all 4?
> Maybe "modules"? Then when I'm just trying to find the code for something
> and cant remember what the dist name is or I want to see an overview of
> everything we include I can look there?
>
> Would that be a step too far?
>

Much of it is functional. In particular "you probably should not commit any
edit in cpan/" is useful.

That said, I do feel your pain, and I think that adding a 5th directory for
perl modules to live in (Nicholas forgot to mention lib) would add more
confusion than it's worth.

Leon

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About