Johan Vromans wrote:
> Ken Williams <[EMAIL PROTECTED]> writes:
>
>> My intention when I added 'build_requires' to Module::Build was not
>> to let people avoid downloading & building those dependencies, but
>> rather to indicate that there was no runtime dependency, ...
>
> For this to function p
On 8/5/06, Ovid <[EMAIL PROTECTED]> wrote:
- Original Message
From: Ken Williams <[EMAIL PROTECTED]>
> BTW, you might want to add a "see also" in the AI::Prolog docs for
> the SWI-Prolog wrapper?
Probably a good idea. It's recommended in AI::Prolog::Article, but that's
about it.
Al
- Original Message
From: Ken Williams <[EMAIL PROTECTED]>
> BTW, you might want to add a "see also" in the AI::Prolog docs for
> the SWI-Prolog wrapper?
Probably a good idea. It's recommended in AI::Prolog::Article, but that's
about it.
Cheers,
Ovid
-- If this message is a respons
On Sat, Aug 05, 2006 at 11:27:09AM +0200, Johan Vromans wrote:
> "A. Pagaltzis" <[EMAIL PROTECTED]> writes:
>
> > That seems wrong. Every module you install contains lists of
> > dependencies, one list for runtime, one for build-time.
> >
> > The CPAN shell won?t ask questions about missing depend
BTW, you might want to add a "see also" in the AI::Prolog docs for
the SWI-Prolog wrapper?
-Ken
On Aug 4, 2006, at 7:22 AM, Joshua ben Jore wrote:
PAUSE says to send problems to modules@perl.org but perl.org's web
page says that's a closed list?! So now this is two problems. One is
why PAU
On Aug 5, 2006, at 4:27 AM, Johan Vromans wrote:
If Test::Ridiculous were not installed, I could chase down the perl
installation to find out what files were added[2], and distribute
these to the production systems. Now I have to manually weed out the
files that are not needed for production.
On Aug 4, 2006, at 10:21 AM, Johan Vromans wrote:
As already mentioned by other people in other threads, if you prepare
install kits for many systems, you would not want to install all the
build-time requirements, only the run-time requirements.
If the "install kit" is essentially a binary di
On Aug 4, 2006, at 8:04 AM, Johan Vromans wrote:
Ken Williams <[EMAIL PROTECTED]> writes:
My intention when I added 'build_requires' to Module::Build was not
to let people avoid downloading & building those dependencies, but
rather to indicate that there was no runtime dependency, ...
For t
"A. Pagaltzis" <[EMAIL PROTECTED]> writes:
> That seems wrong. Every module you install contains lists of
> dependencies, one list for runtime, one for build-time.
>
> The CPAN shell won’t ask questions about missing dependencies,
> that is true. But why does that matter? You have the dependency
>
