# from David Nicol
# on Saturday 12 April 2008 14:15:
>start with an index of packages to distributions,
Like 02package.details.txt?
>grep the module source for C statements, there you are.
The grep will only get you part of the way there. To get everything,
you have to deal with the run-tim
On Fri, Apr 11, 2008 at 5:39 PM, Ricardo SIGNES
<[EMAIL PROTECTED]> wrote:
>
> I don't see a really good way to automate this.
>
> --
> rjbs
start with an index of packages to distributions, grep the module source
for C statements, there you are. The function that converts the list
of use stat
* Gabor Szabo <[EMAIL PROTECTED]> [2008-04-12 08:40]:
> So for what is Catalyst a good example?
I don’t know who meant what. What I know with certainty that is
that Catalyst did get split up.
The way in this happened (the single distro was split into
runtime, dev tools and manual) means that you’
On Sat, Apr 12, 2008 at 1:46 AM, David Cantrell <[EMAIL PROTECTED]> wrote:
> On Fri, Apr 11, 2008 at 06:39:21PM -0400, Ricardo SIGNES wrote:
>
> > In general, listing everything is a good idea -- but there are cases where
> it
> > is just too much work right now. For dists that contain dozens o
On Fri, Apr 11, 2008 at 06:39:21PM -0400, Ricardo SIGNES wrote:
> In general, listing everything is a good idea -- but there are cases where it
> is just too much work right now. For dists that contain dozens of modules,
> all
> of which are very unlikely to ever be split up, it's not very inter
* Thomas Klausner <[EMAIL PROTECTED]> [2008-04-11T13:07:30]
> On Fri, Apr 11, 2008 at 03:10:05PM +0200, Dominique Quatravaux wrote:
> > On Fri, Apr 11, 2008 at 1:04 PM, Gabor Szabo <[EMAIL PROTECTED]> wrote:
> > > So if I am using Tk::Widget::A and Tk::Widget::B... Tk::Widget::Z all
> > > provide
Hi!
On Fri, Apr 11, 2008 at 03:10:05PM +0200, Dominique Quatravaux wrote:
> On Fri, Apr 11, 2008 at 1:04 PM, Gabor Szabo <[EMAIL PROTECTED]> wrote:
> > So if I am using Tk::Widget::A and Tk::Widget::B... Tk::Widget::Z all
> > provided by Tk.
> > Should I add all of them as prerequisite of my mo
Gabor Szabo wrote:
So if I am using Tk::Widget::A and Tk::Widget::B... Tk::Widget::Z all
provided by Tk. Should I add all of them as prerequisite of my
module or should I add only Tk?
Given the expanding list of dual-lived modules, I've started listing all
dependencies, including core ones.
On Fri, Apr 11, 2008 at 1:04 PM, Gabor Szabo <[EMAIL PROTECTED]> wrote:
> So if I am using Tk::Widget::A and Tk::Widget::B... Tk::Widget::Z all
> provided by Tk.
> Should I add all of them as prerequisite of my module or should I add only
> Tk?
I'd prefer for CPANTS to allow both. TIMTOWTDI.
On Fri, 2008-11-04 at 14:04 +0300, Gabor Szabo wrote:
> I have started to outline the recommended way of doing this here:
> http://www.perlfoundation.org/perl5/index.cgi?cpan_packaging
> but of course your input is highly appreciated.
It looks good to me. The only nit I have is that everyone is w
I say list them all, but we should encourage tools to make that
easier/automatic. It could be done at "make dist" time just like the
rest of META.yml unless the author overrides it.
Personally, I have a script which searches for modules and prints them
in the right format, plus adds either the cu
Hi,
we have been discussing with Domm how CPANTS should check if a
distribution declares each of its prerequisites correctly which brought
us to the the point that we have a problem.
Let's focus for now only on dependencies on other CPAN modules and
not on external libraries.
So if I am using Tk:
12 matches
Mail list logo
