On Fri, Jan 11, 2008 at 10:27:17AM +0800, Emfox Zhou wrote:
> Ming Hua <[EMAIL PROTECTED]> writes:
>
> > The best solution would be teaching upstream to understand the SONAME
> > issue and bump it. Or we can make it a private library (but I don't
> > really know how). Or make very strict dependency between the
> > applications and the library.
>
> It's up to the upsteam, strict dependency is the best solution now.
>
> > Let me know what you think,
>
> According to my knowledge, the lib is just for sharing between pcmanx-gtk2
> and mozilla-plugin-pcmanx, and upstream do not have plan to open the API
> for generic use, so I'd change the dependency.
>
> But it seems there is no good way to solve the current problem, that is, we
> cannot stop people from upgrading libpcmanx-core0 but keep pcmanx-gtk2, or
> if you have good suggestion, do please tell me.
Looking at 0.3.7-2 (I haven't read the source), it seems you've made the
dependency very strict, something like (= {binary:Version}). This
should stop people from upgrading libpcmanx-core0 and keeping old
pcman-gtk2, shouldn't it?
Ming
2008.01.11
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
