But I'm not really too worried any more, the CamelPack means it's much
easier not to just install from source than use the PPM system.
s/not/now/
sigh
Adam K
On 2/6/06, Adam Kennedy wrote:
>
> > But I'm not really too worried any more, the CamelPack means it's much
> > easier not to just install from source than use the PPM system.
>
> s/not/now/
>
Installing from souce == compiling every module that needs it... How
is that *easier* than installing a p
* Offer Kaye <[EMAIL PROTECTED]> [2006-02-06 09:15]:
>Installing from souce == compiling every module that needs it...
>How is that *easier* than installing a pre-compiled package?
You don’t need sit there turning a crank while the compiler does
its job. Does it take longer? Sure. Is it harder? No
Offer Kaye writes:
> On 2/5/06, Offer Kaye wrote:
>
> > [http://ppm.activestate.com/BuildStatus/5.8-windows/windows-5.8/Scalar-List-Util-1.15.txt
>
>
> Something funky here... Last night I looked at "Scalar-List-Util"...
> but the correct name as Tyler said is "Scalar-List-Utils", with an "s"
Offer Kaye writes:
> I see what you mean... what threw me off was that [List::Util and
> Scalar::Util are] not listed under:
> http://search.cpan.org/dist/perl-5.8.8/
Well spotted! List/Util.pm (including pod) is here:
http://search.cpan.org/src/NWCLARK/perl-5.8.8/ext/List/Util/lib/List/Util.
On 2/5/06, Offer Kaye <[EMAIL PROTECTED]> wrote:
> BTW Gozer have you looked at the first line:
> Cannot forceunlink D:\cpanrun\build\5-8-0\lib\auto\List\Util\Util.dll:
> Permission denied at D:\cpanrun\build\5-8-0\lib/File/Find.pm line 874
>
> Maybe the script is trying to delete a file that the s
On 2/6/06, Smylers wrote:
>
> So it seems the extra level of subdirectories are causing List::Util
> (and a whole bunch of other modules) not to show up in the main perl
> dist page.
>
> Is Cpan Search's heuristic for what gets included documented anywhere?
Now that I think about it, I seem to rec
On Feb 6, 2006, at 1:37 AM, Adam Kennedy wrote:
In fact, what you just asked is already listed in the PITA
documentation as within it's scope.
For lack of a better name, I've called it Fallout Testing.
As opposed to Rot Testing, which is when your module doesn't
change, but makes sure it s
David Landgren wrote:
David Cantrell wrote:
brian d foy wrote:
Seriously though, I would expect things in Win32::* to only work on
Windows, things in Linux::* only to work on linux, and so on for many
other sections (including Mac::* where I have some modules). Portable
code isn't always the g
Offer Kaye wrote:
On 2/6/06, Adam Kennedy wrote:
But I'm not really too worried any more, the CamelPack means it's much
easier not to just install from source than use the PPM system.
s/not/now/
Installing from souce == compiling every module that needs it... How
is that *easier* than inst
10 matches
Mail list logo