Andras Barna writes: > yeap > they have libtorrent-rasterbar.so for libtorrent-rastebar > and for rakshasa's simply libtorrent. so we can go this way too (if > noone has other idea(s))
If the library isn't really well-accepted in the open source community (i.e., it has just one consumer *and* there's an alternative that has many consumers), then making it a static library makes a lot more sense to me. That way, you don't have to deal with either the package naming or the /usr/lib real estate issues. You can always break it back apart later and deliver it as a dynamic library if you find that someone else needs it. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
