application-specific shared libs?
> First one: it means you have a shared library in your package without
> providing dependency information about it. In this case it shouldn't
> cause a problem because the shared object looks like it'll only be
> used by rosegarden.
Aha. Fixed, thanks.
Can anybody give me a rundown on the policy about application-specific
shared libraries? Petal.so provides an internal Rosegarden scripting
language, which is pretty useless without Rosegarden. Should I still
split it into libpetal and libpetal-dev? Right now I've just been dumping
Petal.so into /usr/X11R6/lib/rosegarden ...
It's also a tcl library. Which means you don't generally link C code to
it -- so would it need a -dev package?
Will
--------------------------------------------------------------------------
| harpo@udel.edu lowe@cis.udel.edu lowe@debian.org |
| http://www.cis.udel.edu/~lowe/ |
| PGP Public Key: http://www.cis.udel.edu/~lowe/index.html#pgpkey |
--------------------------------------------------------------------------
| You think you're so smart, but I've seen you naked |
| and I'll prob'ly see you naked again ... |
| --The Barenaked Ladies, "Blame It On Me" |
--------------------------------------------------------------------------
Reply to: