On Fri, Feb 06, 2004 at 10:29:33AM -0500, Greg Folkert scribbled: > On Fri, 2004-02-06 at 06:54, Sebastian Ley wrote: > > Hi all, > > > > presently we have two two (at least) javascript libraries in debian, > > one NGS javascript interpreter and one from the spidermonkey > > interpreter. Upstream, both parties use libjs as library name. With > > the NGS interpreter being first packaged for debian, the maintainer of > > the spidermonkey libs chose to rename the library to libsmjs. That is > > now highly inconvenient for me, building a package against the > > library, because I have to patch the upstream sources to use the new > > name for the library. > > > > What would be a good way to deal with the situation? Is it sufficient > > to let both packages conflict with each other? > Zounds.... This sounds like a job for our Super Hero:\ > "update-alternatives" > > And having both packages use unique names and then you choose your > alternative. And thus breaking any package linked against the other library... marek
Attachment:
signature.asc
Description: Digital signature