Re: [MacPerl-Porters] compile/install/test problem

[Paul Schinder <schinder@pobox.com>]

At 6:10 PM -0600 1/18/00, Matthew Langford wrote:
>On Tue, 18 Jan 2000, Paul Schinder wrote:
>
>  > >Here's my blib structure:
><snip>
>  > >Is this right?
>  >
>  > In a proper blib the architecture dependent things go in blib/arch,
>  > but the way you have it looks like it will work.
>
>Oh.  I was basing the structure on other modules, like XML::Parser and
>Text::CSV, that I got from MMP.  Will installme.plx do the right thing if
>it encounters blib/arch?

Don't know for sure.  But I just realized that we have an unusual 
"two arches for the price of one" situation here, so leaving it the 
way you have may be best.

>
>
>  > >Who are the usual suspects in this case?
>  >
>  > Wrong @INC.  You might want to put a "print "@INC";" at the beginning
>  > of the test just to make sure that the test script is seeing the
>  > right one.  Since handler is actually done by the XS, the other
>  > possibility is that the shared library isn't loading, but I'd expect
>  > a DynaLoader error in that case.
>
>D'oh!  Yes, in spite of all Chris Nandor's warnings about this, I had let
>"lib" sneak in front of "site_perl:lib".  I wonder how that happened?
>
>Thanks for the help.
>
>
>  > You probably don't want to hear that HTML-Parser-3.04 is out :-)
>
>More blue sky dreaming...
>Once I've gotten a module to compile, it doesn't take much work to pop in
>a new version and recompile.  I wonder if it's possible to use push
>technology (isn't XSV an XML-ized server push "channel"?) to subscribe to
>updates, automatically download, and recompile?


I'm sure it's possible, but it's a matter of whether you think it's 
worth doing.  I've always found automatic updaters a little scary, 
and usually turn them off.  I use Apple's Software Updater in MacOS 
9, and Norton Utilities Live Update, but I always run them by hand. 
That way I can wait a few days to see if there are any problems with 
the new versions.  With Perl, on the other hand, I get some 
protection from the regression tests that most everything I install 
have, so I don't worry quite as much about it.  (The fact that a bad 
Perl module isn't as dangerous as a bad Apple extensions also comes 
into play...)..

>
>Like an active "push" CPAN, which would ask if you wished to update
>modules X,Y,Z,... which had updates available.  Of course you can look for
>updates with CPAN, but already doing the search, and prompting for an
>automated update, might be handy.  Some provision would need to be made
>for modules the CPAN user wished to keep perpetually out of date (GD-Gif
>or Zlib, for example), to prevent the prompting from becoming a pest.
>
>
>
>--
>MattLangford

--
Paul Schinder
schinder@pobox.com

==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe" to macperl-porters-request@macperl.org