On Mon, Dec 23, 2013 at 04:05:15PM +0100, Ingo Schwarze wrote: > Andrew Fresh wrote on Sun, Dec 22, 2013 at 06:24:17PM -0700: > > On Mon, Dec 23, 2013 at 01:32:54AM +0100, J'er'emie Courr`eges-Anglas wrote: > > >> I thought that this module only fetched data and fed it into our base > >> pod formatter, but if it does more that may be a better choice indeed. > > > As far as I know the above is correct. It overloads the standard > > Pod::Perldoc's ->searchfor method and if it doesn't find a local > > document, pulls the module from metacpan into a temporary file and > > displays it. > > My point being that categorization makes most sense by purpose, and > the purpose is to display manuals, and many tools to display manuals > or prepare them for display live in textproc. I'd consider putting > it below "net" because of the way it is technically working - opening > a network connection to download some data - to be excessively > formalistic. Devel is not only crowded, but misleading because > the port is unusable for code development; it's puropose isn't even > documentation development, but if it were, tools for documentation > development live in textproc as well. Sysutils - well, merely > displaying a manual is not really a task of system administration...
I'm fine with textproc, I generally use pkg_add or cd /usr/ports/*/p5-Pod-Cpandoc so it doesn't really matter. Based on discussion and my thoughts, I would probably put it in net as primary due to the way it works, but also tagged sysutils as I think reading docs is part of system administration and the main piece of this port is /usr/local/bin/cpandoc. Again, l8rZ, -- andrew - http://afresh1.com Hey, I think I see a barn up ahead. -- The American Astronaut
