Re: How to declare dependency on other modules?
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 of modules, all of which are very unlikely to ever be split up, it's not very interesting or useful for an author to list everything he uses. Tk and Catalyst are good examples. Catalyst is an excellent example. I'm sure it has gone through at least one fairly major re-organisation of its distributions at some point. So for what is Catalyst a good example? If I understand RJBS said it is a good example for a distro that *does not* get split up while from David I understood it *did*. So am I just falling in the crack between US and UK English or did you really say the opposite? Gabor
Re: How to declare dependency on other modules?
* 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’re unlikely to have trouble from undeclared dependencies on modules that were present in the all-in-one package but got moved into different distros on split. However, one of the reasons for the split was to minimise the number of distros you’d have to install on a server to run a Cat app – much of the huge dependency tree of Catalyst was only required by the dev tools. So if you were lazy and relied on your Catalyst dependency pulling in all those other kitchen sinks, then after the split your app would no longer install. Regards, -- Aristotle Pagaltzis // http://plasmasturm.org/
Re: How to declare dependency on other modules?
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 Cuse statements, there you are. The function that converts the list of use statements into the dependency list would be yet another thing that the cpan.org web site does, and creating the draft section of the Makefile.PL file or equivalent could be achieved, from the module author's perspective, with something like make cpandep.
