Tim Bunce wrote:
If there's a libfoo.so and I want to create a perl module/distribution
that's just a very thin wrapper around libfoo, what should I call it?
LibFoo
Lib::Foo
Lib::foo
Lib::libfoo
libfoo
SomeCategory::Libfoo
???
Following the "Category::Foo" scheme:
- libpcap -> Net::Pcap
- libdnet -> Net::Libdnet
- libxml2 -> XML::LibXML
- libxslt -> XML::LibXSLT
- Xerces -> XML::Xerces
- OpenSP -> SGML::Parser::OpenSP
- libmagick -> Image::Magick
- libkakasi -> Text::Kakasi
- zlib -> Compress::Zlib (same for the other compression libs:
Bzip2, LZF, LZW)
- OpenSSL -> Net::SSLeay / Crypt::SSLeay
- MatrixSSL -> Crypt::MatrixSSL
- libsyck -> YAML::Syck / JSON::Syck
- PARI -> Math::Pari
- libtidy -> HTML::Tidy
- libusb -> Device::USB
Following the top-level namespace "Foo" scheme:
- libdb (BerkeleyDB) -> DB_File (v1) / BerkeleyDB (v2, 3, 4) / BDB
(v4)
- libev -> EV
- OpenGL
- Ogre, OIS (game libs)
- all the GUI toolkits: Tk, TkZinc, Gtk2, Wx, Qt, Prima
Eric Whilhem wote:
Seems like Alien would be the place for that. If it goes by e.g.
libpng, then Alien::libpng seems natural.
Alien dists seem to be currently more for installing things more
"alien" than mere libs. Out of the 14 Alien distributions on the
CPAN, 8 are for installing JavaScript libraries, 2 are for Selenium,
1 for SVN Perl bindings, 1 for WxWidgets. As a sysadmin, I prefer to
install the external libs by myself, or in case of packaging, make
sure the needed libs are indicated as prerequisites.
--
Sébastien Aperghis-Tramoni
Close the world, txEn eht nepO.
