On Mon, Sep 12, 2005 at 03:03:02AM -0700, Steve Langasek wrote:
> On Mon, Sep 12, 2005 at 11:34:22AM +0200, Domenico Andreoli wrote:
> > will libcurl3 with versioned symbols break existing packages linked
> > to it?
>
> It will not.
good
> It would be best to coordinate with upstream to get symb
On Mon, Sep 12, 2005 at 11:34:22AM +0200, Domenico Andreoli wrote:
> will libcurl3 with versioned symbols break existing packages linked
> to it?
It will not.
It would be best to coordinate with upstream to get symbol versioning
added there as well, so that binaries built against the symbol-versi
On Sun, Sep 11, 2005 at 09:46:26PM -0700, Thomas Bushnell BSG wrote:
> Paul TBBle Hampson <[EMAIL PROTECTED]> writes:
>
> > Mind you, the license/OpenSSLCallback conflict neccessarily
> > segregates the packages into two camps, those which are GPL, and
> > those which need the callback only suppli
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes:
> On Sat, 10 Sep 2005, Thomas Bushnell BSG wrote:
>> It is *absolutely intolerable* to declare such conflicts for shared
>> libraries, where there are easy solutions: MAKE TWO LIBRARIES THAT
>> HAVE DIFFERENT NAMES.
>
> The package has to bui
On Sun, 11 Sep 2005, Domenico Andreoli wrote:
> On Sun, Sep 11, 2005 at 10:54:17AM -0300, Henrique de Moraes Holschuh wrote:
> > On Sat, 10 Sep 2005, Thomas Bushnell BSG wrote:
> > > It is *absolutely intolerable* to declare such conflicts for shared
> > > libraries, where there are easy solutions:
On Sun, Sep 11, 2005 at 10:54:17AM -0300, Henrique de Moraes Holschuh wrote:
> On Sat, 10 Sep 2005, Thomas Bushnell BSG wrote:
> > It is *absolutely intolerable* to declare such conflicts for shared
> > libraries, where there are easy solutions: MAKE TWO LIBRARIES THAT
> > HAVE DIFFERENT NAMES.
>
On Sat, 10 Sep 2005, Thomas Bushnell BSG wrote:
> It is *absolutely intolerable* to declare such conflicts for shared
> libraries, where there are easy solutions: MAKE TWO LIBRARIES THAT
> HAVE DIFFERENT NAMES.
The package has to build libraries with differently versioned symbols as
well, to avoid
Thomas Bushnell BSG <[EMAIL PROTECTED]> writes:
> There should be TWO libcurls, with DIFFERENT names, and then
> applications can simply link against whichever one they want, instead
> of the current approach, which totally breaks, violates policy, and
> doesn't really help much of anyone.
I real
8 matches
Mail list logo