Namespace Query: SYSV package creation

I've been developing a script that creates SYSV packages from CPAN sources using CPANPLUS. In the process, I've developed a few bits of code that should be abstracted out into a seperate module so that others (for example, alien ) can use the code to create

XML::XSLT

I've put XML::XSLT v. 0.31 on CPAN. This is a module that a group of developers on Sourceforge have been working on (at a snail's pace or worse) for a while. Brong Gondwana (CPAN id: BRONG) uploaded the last release, but I haven't heard from him in a while, so I've uploaded v 0.31. Would it be

Address Book

This time, I'm doing it right and getting a namespace before really going anywhere with the project. I'm working on a web-based, LDAP-backed contacts organizer system for a client. I noticed http://ldap-abook.sourceforge.net/ and thought that it was a good starting point. Now come the namespac

Re: IO::PgLoFile

> "TB" == Tim Bunce <[EMAIL PROTECTED]> writes: TB> None at all. I'd expect that generic module to be called TB> IO::BLOB but to use the services of Pg::*, Oracle::*, TB> MySQL::*, and DBI. Thanks for te clarification. Mark.

Re: IO::PgLoFile

> "TB" == Tim Bunce <[EMAIL PROTECTED]> writes: >> Make that IO::BLOB::Pg. TB> Or Pg::* Granted this is PostgreSQL-specific, but there is, AFAIK, nothing to stop someone from developing something similar for, say, Oracle. That, and it is IO-oriented. It seems to fit quite nicely a

Re: IO::PgLoFile

>>>>> "MAH" == Mark A Hershberger <[EMAIL PROTECTED]> writes: MAH> Can I have the IO::PgLoFile namespace? Make that IO::BLOB::Pg. In case people want to build something similar for another DB. Or should that be IO::Blob::Pg? Mark.

IO::PgLoFile

e more difference compared to IO::Handle, is that the write() and syswrite() methods allow the length argument to be left out. BUGS The perl TIEHANDLE interface is still not complete. There are quite a few file operations that will not yet invoke any method on the tied object. See t