On Mon, Nov 14, 2005 at 01:06:37PM +0100, Torsten Marek wrote: > > [Justin] > > Should perl modules also be shlibs? How about /etc/bash_completion? > > If the category is meant to include anything that can be used as > > modular code, can we please have the name changed to something other > > than "shlib"? > I'm afraid I disagree with you here. As long as code is meant to be used by > more > than one application by definition (as most Perl or Python modules, that > install > their code in /usr/lib/pythonx.y/site-packages/ and do not carry an > executable), > they are shared libraries.
As I understand those tags, 'role::sw:shlib' is that shared code that's required by programs to function but is not useful otherwise; if I could use one of those packages directly when doing development, then it'd be role::sw:devel-lib. So, I'd tag the python2.n-foobar packages as 'role::sw:devel-lib', because even if they contain what technically is shared libraries (which however are dlopened by python rather than resolved by ld), they also contain documentation and they can be used when doing development. As a consequence, libfoo0 can safely be hidden in a package manager (it's only useful as a dependency), while python2.n-foobar would instead be useful for python development and shouldn't be hidden. > Maybe it would be a good thing to start a wiki page with annotation/tagging > guidelines. I'll try to find some time to boostrap one. Oh, yes. I'd put most of the information in the tag and facet descriptions if possible, but more general guidelines (including, maybe, also "check the tag/facet description" :) ) could really be worth being collected in a wiki page at wiki.debian.org. Ciao, Enrico -- GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
_______________________________________________ Debtags-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debtags-devel
