Groups | Search | Server Info | Login | Register


Groups > perl.module-authors > #3358

Re: tools and work flows for developing collections of distributions

Newsgroups perl.module-authors
Subject Re: tools and work flows for developing collections of distributions
References <4ea6e6aa-f708-af10-69a2-3265793ed72b@holgerdanske.com> <20181121101549.GA9430@bytemark.barnyard.co.uk> <5e8b5b5f-a3f0-756d-9d0e-1207efcc6a4d@holgerdanske.com> <20181122103143.GB10971@bytemark.barnyard.co.uk>
Message-ID <9c00ef1a-d3aa-a6ee-ce2d-9e5c3534ff4c@holgerdanske.com> (permalink)
Date 2018-11-23 00:25 -0800
From dpchrist@holgerdanske.com (David Christensen)

Show all headers | View raw


On 11/22/18 2:31 AM, David Cantrell wrote:
> On Wed, Nov 21, 2018 at 02:50:26PM -0800, David Christensen wrote:
>> On 11/21/18 2:15 AM, David Cantrell wrote:
>>> These days people tend to just create Task-whatever
>>> distributions, which contain a bit of documentation in Task::whatever
>>> for the benefit of metacpan users, and the usual Makefile.PL to declare
>>> dependencies.
>> Where can I find documentation that explains Tasks and how to create them?
> 
> The same place you'd find documentation on creating any other completely
> normal distribution.
> 
>> I assume you are referring to the PREREQ_PM argument to WriteMakefile().
>> As I understand it, this argument assumes that the modules are already
>> installed.
> 
> A CPAN client will spot the dependencies and install them.
> 
>>             So for development, I would need to preface the Perl include
>> path with the 'lib' directories for each of my distribution source trees
>> (?).
> 
> If you want to test against stuff that isn't on the CPAN, yes. If you
> have all your distributions' sources as sub-dirs of a single directory
> you can do something like ...
> 
>    cd $wherever
>    export PERL5LIB=`perl -MCwd -e 'print join(":", map { cwd."/$_/lib" } @ARGV)' *`:$PERL5LIB
> 
> but note that that won't work for stuff that has XS components, or where
> Makefile.PL does funky stuff to edit your code, or where your source
> code isn't laid out in the normal hierarchy. Also on at least some
> platforms there is a limit on how long PERL5LIB can be.

Okay.


David

Back to perl.module-authors | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

tools and work flows for developing collections of distributions dpchrist@holgerdanske.com (David Christensen) - 2018-11-20 17:25 -0800
  Re: tools and work flows for developing collections of distributions david@cantrell.org.uk (David Cantrell) - 2018-11-21 10:15 +0000
    Re: tools and work flows for developing collections of distributions dpchrist@holgerdanske.com (David Christensen) - 2018-11-21 14:50 -0800
      Re: tools and work flows for developing collections of distributions david@cantrell.org.uk (David Cantrell) - 2018-11-22 10:31 +0000
        Re: tools and work flows for developing collections of distributions dpchrist@holgerdanske.com (David Christensen) - 2018-11-23 00:25 -0800
  Re: tools and work flows for developing collections of distributions shlomif@shlomifish.org (Shlomi Fish) - 2018-11-21 19:28 +0200
  Re: tools and work flows for developing collections of distributions dpchrist@holgerdanske.com (David Christensen) - 2018-11-21 17:26 -0800

csiph-web