Re: Let's eliminate the Module List
On Thu, 2004-08-19 at 13:54, Simon Cozens wrote: [EMAIL PROTECTED] (Jose Alves de Castro) writes: I don't want to show the results of a search. I want to say Here is the link to the module list. See how long it is? It contains practically everything you need, doesn't it? http://www.cpan.org/modules/02packages.details.txt.gz Hmmm that is pretty complete. Good point. I kind of like the idea of a standard KEYWORDS section for PODs... Gives the author ability to help a potential user find the module. Sort like man -k. Adding (say up to 10?) keywords after the tarball name would make _this_ pretty useful... It would be useful for an enhancement to search.cpan,org org too.
Re: Let's eliminate the Module List
Christopher Hicks wrote: On Thu, 19 Aug 2004, Hugh S. Myers wrote: 2. Push hard on the notion of adding a keywords item to the 'standard' for pod documentation. What should those keywords be? Who decides? I'm personally much more interested in seeing a dmoz-ish hierarchy so related modules can be easily found and compared. I agree[1]. A static list of catagories like DMOZ or SourceForge uses would provide for improved, more consistent searches and an improved by-catagory browsing catalog. Catagories could be added to META.yml for easy indexing by search.cpan.org. Fixed catagories make it more likely that similar modules will be found together both when browsing by-catagory and when searching. And you eliminate the abuses of keywords. 1. http://www.nntp.perl.org/group/perl.module-authors/2601/
Re: Let's eliminate the Module List
On Thu, 2004-08-19 at 18:54, Simon Cozens wrote: [EMAIL PROTECTED] (Jose Alves de Castro) writes: I don't want to show the results of a search. I want to say Here is the link to the module list. See how long it is? It contains practically everything you need, doesn't it? http://www.cpan.org/modules/02packages.details.txt.gz It seems like I'm the only one, but I still prefer the other list... :-( It has the module descriptions and all... :-( -- José Alves de Castro [EMAIL PROTECTED] http://natura.di.uminho.pt/~jac signature.asc Description: This is a digitally signed message part
Re: Perspectives on a Namespace
Hi, What about DB_File::Clean instead? Either you have a function to which you can give diffrent types of cleaning operations or you may have multiple modules to do the different operations. As an example (certainly incorrect as I don't have the slightess clue of what you can clean in a DB file), you could have DB_File::Clean::HashKeys, DB_File::Clean::HashData, DB_File::Clean::Something. You could also have this type of interface if you wish to: use DB_File::Clean ; DB_Clean( $handle to db, qw(DB_File::Clean::Hash Data DB_File::Clean::Something)) ; or DB_Clean( $handle to db, qw( HashData Something)) ; and your module would automaticaly load the special cleaning modules passed as parameters. This is what I do in one of my modules. # loads Data-TreeDumper-Renderer-DHTML automatically. DumpTree($tree, 'Tree', RENDERER = 'DHTML'); Cheers, Nadim. Luis Tello [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hello, My name is Luis. I have been using a module called DB_File::Lock for the past year on a project. I was asked by my employeer to develop a way to remove data not associated with a hash in a dbm file. The objective was to streamline a dbm file because using the remove function only removes the hash and not the data associated to the hash. I was successful in creating the module and now I want to prepare it for distribution. Under the advice of the PAUSE page, I am asking for your perspective on a namespace. I was think DB_File::GarbageRemoval or DBM::GarbageRemoval. What do you think? thanks, Luis __ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail
Re: META.yml generation and SIGNATURE problems
Kjetil Kjernsmo writes: Hi all! I'm a relatively fresh CPAN author who wants to start signing his modules. And I'm pretty confused about how to do it, and asking some friends, they told me to go here. I I'm not subscribed, so please CC any replies. I first tried to sign my AxKit::App::TABOO, and the signing itself is straightforward with Module::Signature's cpansign. I build the module like I've always done, with make dist, using ExtUtils::MakeMaker, I suppose. Everything looks fine, but then I notice that META.yml has changed, and it invalidates the signature... So, I figured, the build process must be split up in several steps. Since it is make distdir that creates META.yml, then cpansign should be run after that, but then, it copies everything to the new dir too, so it is sort of too late to sign...? Uhm, well, I'm confused... I think it would have been great if the signing was integrated in the make dist process somehow, but in the meantime, is there a simple and reliable way to do this...? I don't have much experience, but the following works for me: ; perl Makefile.PL ; make distdir ; rm Makefile ; rm -rf Directory created by make distdir ; cpansign sign ; make distdir I use make dist for the last step, but same thing. SIGNATURE must be in the MANIFEST and a SIGNATURE file must exist for the first make distdir, touch SIGNATURE is good enough to bootstrap. To sanity check you may want to do: ; cd Directory created by make distdir ; cpansign To make sure it all went well... -- Sam Holden
name for singlethreaded web server framework module
I am writing a module that provides HTTP interface using select, for simple web applications without a web-server, and without POE or other modules. Configuration will be by mapping paths to coderefs. Planning to call this cute beastie HTTP::Server::Selecting. Comments? -- david nicol Someday, everything's going to be different when I paint my masterpiece.
