John Levon wrote: > On Tue, Apr 01, 2008 at 08:34:20AM -0700, Ethan Quach wrote: > >> One thing I'm noticing on a current Solaris x86 box is that there seems >> to be a >> couple other conventions. Given a /usr/lib/libfoo.so.1, there are a >> couple cases >> of /usr/lib/python2.4/vendor-packages/foo.so or >> /usr/lib/python2.4/vendor-packages/libfoomod.so > > Well spotted. Note that the libfoomod.so variants are all written by the > same person, and they all have .py files in the same directory. So I > don't think this applies here. > > Without the 'lib' part you'd have 'be.so', which seems a little too > generic, so 'libbe.so' is the naming that makes most sense to me. I'm > open to differing opinions... >
We changed the name to be libbe.so and it lives in /usr/lib/python2.4/vendor-packages since it will be used by at least two different apps, beadm(1M) and eventually pkg(1). Thanks Tim > regards, > john
