Hi again, > hmmmm... if you (I too) can't see it on search.cpan.org, how do you > know 0.24 exists? I searched on the minimalist seargent.org, and on > Google too... nothing about 0.24. Is there a secret place? ;-)
Hmm, not very sEcReT; Matt Sergeant has a use.perl.org journal http://use.perl.org/~Matts/journal/ He happened to mention the new release some time in the last couple of days, and having had the "bus error" joy with SQLite the info stuck in my brain. > on a related note -- I am fairly confused about this CPAN installing > thing? most perl packages (such as SQLite.pm, provided it didn't have > to build libsqlite.a) are just text files, no? Hence, why do they need > to be "installed" unless "install"-ing means simply copying them to the > correct place. For pure perl modules that's pretty much what's up. You can do it yourself if you *really* want to (that used to be the way with things on Mac OS before Chris Nandor wrote some nice tools to do the easy things automatically). If you really want to know what's being done then have a gander at the Makefile that's produced via a "perl Makefile.PL" call. > And, is the "install" procedure merely "perl > Makefile.PL, make, make install"... is that all that CPAN really does > (provided it doesn't have to follow any dependencies). So, if I have to > install something outside of CPAN, do I do "perl Makefile.PL, make, > make install"? All going well that's what CPAN is doing for you: if you watch the procedure you'll notice exactly that sequence being executed, but with the worthwhile twist that it'll postpone installing one module until it's tried to install the prerequisites (and so on). CPAN uses all the standard locations, so installing by hand is perfectly in harmony with the CPAN installation process. It's just significantly more painful if you find dependencies (and then dependencies of dependencies...). In short: yep, "perl Makefile.PL ; make ; make test ; make install". Don't forget the "make test" piece of the puzzle. Habit has me using "sudo make install" at the last step, but just glancing through the directories suggests that the sudo call shouldn't be necessary on Mac OS X. Cheers, Paul
