Tony Cook <[EMAIL PROTECTED]> writes:
> On Wed, Jul 02, 2008 at 08:37:21PM -0400, David Golden wrote:
> > On Wed, Jul 2, 2008 at 7:18 PM, Tony Cook <[EMAIL PROTECTED]> wrote:
> > > Now, this won't continue to be a problem for POE-XS-Loop-Poll, since a
> > > function interface has been added to POE-Test-Loops, but it does
> > > strike me as a bug in the test environment that it doesn't the make
> > > binaries a distribution installs visible during testing.
> >
> > I'm not clear why that makes sense. There's no guarantee that any
> > given $^X is in $ENV{PATH} -- and binaries are installed in the same
> > directory as $^X. So POE-Test-Loops or whatever needs to locate the
> > binary relative to $^X and not rely on $ENV{PATH}.
>
> Going by that logic I'd need to look in $Config{installsitebin},
> $Config{installvendorbin} etc, since $^X could be in installvendorbin,
> while most CPAN installed binaries are likely to be in installsitebin.
>
> Unfortunately this doesn't help in a test environment, since testers
> don't install the binaries in any of those locations.
>
They do. After all, a test environment is usually almost
indistinguishable from a normal environment.
The only problem I see is if a tester is testing only, but never
installing, or if a user is first building and testing and finally
installing everything using CPAN's install_tested command. In this
case the script is neither available in $ENV{PATH} nor in the final
location.
Regards,
Slaven
--
Slaven Rezic - slaven <at> rezic <dot> de
BBBike - route planner for cyclists in Berlin
WWW version: http://www.bbbike.de
Perl/Tk version for Unix and Windows: http://bbbike.sourceforge.net
