On Mon, Apr 14, 2003 at 09:34:48PM +0200, Christian Hammers wrote:
> On Mon, Apr 14, 2003 at 06:23:24PM +0200, Marek Habersack wrote:
> > > > > > The only viable approaches seem to be (in random order)
> > > > > >
> > > > > > * fork libmysqlclient
> > > > > > * convince the MySQL folks to revert
On Mon, Apr 14, 2003 at 06:23:24PM +0200, Marek Habersack wrote:
> > > > > The only viable approaches seem to be (in random order)
> > > > >
> > > > > * fork libmysqlclient
> > > > > * convince the MySQL folks to revert their license change
> > > > > * switch to postgres
> > > > > * get upstream
On Mon, Apr 14, 2003 at 04:16:12PM +0200, Christian Hammers scribbled:
> On Mon, Apr 14, 2003 at 04:10:11PM +0200, Francesco P. Lovergine wrote:
> > > > > So, what *am* I supposed to do? Rebuild against libmysqlclient12
> > > > > and break licenses? Not rebuild and have an uninstallable
> > > > >
On Mon, Apr 14, 2003 at 05:37:15PM +0200, Joerg Wendland wrote:
> Steve Langasek, on 2003-04-14, 09:38, you wrote:
> > There's also no wiggle room for "indirect linking" arguments, because
> > Debian is distributed as a cohesive whole: if we distribute GPL app foo
> > linked against LGPL library ba
Steve Langasek, on 2003-04-14, 09:38, you wrote:
> There's also no wiggle room for "indirect linking" arguments, because
> Debian is distributed as a cohesive whole: if we distribute GPL app foo
> linked against LGPL library bar, and Debian's copy of libbar is linked
> against OpenSSL, you cannot a
On Mon, Apr 14, 2003 at 04:10:11PM +0200, Francesco P. Lovergine wrote:
> On Tue, Apr 15, 2003 at 12:05:49AM +1000, Hamish Moffatt wrote:
> > On Mon, Apr 14, 2003 at 01:30:26PM +0200, Wichert Akkerman wrote:
> > > Previously Sander Smeenk wrote:
> > > > So, what *am* I supposed to do? Rebuild again
[Should this thread be carried over to debian-devel?]
On Mon, Apr 14, 2003 at 01:25:28PM +0200, Sander Smeenk wrote:
> Quoting Wichert Akkerman ([EMAIL PROTECTED]):
> > Previously Marek Habersack wrote:
> > > What about a case as mine - Pike 7.4 is MPL/GPL/LGPL. How does that look
> > > in
> > >
On Mon, Apr 14, 2003 at 04:10:11PM +0200, Francesco P. Lovergine wrote:
> > > > So, what *am* I supposed to do? Rebuild against libmysqlclient12
> > > > and break licenses? Not rebuild and have an uninstallable snort-mysql?
> > >
> > > The only viable approaches seem to be (in random order)
> > >
On Tue, Apr 15, 2003 at 12:05:49AM +1000, Hamish Moffatt wrote:
> On Mon, Apr 14, 2003 at 01:30:26PM +0200, Wichert Akkerman wrote:
> > Previously Sander Smeenk wrote:
> > > So, what *am* I supposed to do? Rebuild against libmysqlclient12
> > > and break licenses? Not rebuild and have an uninstalla
On Mon, Apr 14, 2003 at 01:30:26PM +0200, Wichert Akkerman wrote:
> Previously Sander Smeenk wrote:
> > So, what *am* I supposed to do? Rebuild against libmysqlclient12
> > and break licenses? Not rebuild and have an uninstallable snort-mysql?
>
> The only viable approaches seem to be (in random
On Mon, Apr 14, 2003 at 01:25:28PM +0200, Sander Smeenk wrote:
> Should we massively ask permission to explicitly link against OpenSSL
> from the OpenSSL upstream? It was something like that, right? You were
> supposed to ask permission to link against OpenSSL.
No, you need permission from the aut
Previously Sander Smeenk wrote:
> So, what *am* I supposed to do? Rebuild against libmysqlclient12
> and break licenses? Not rebuild and have an uninstallable snort-mysql?
The only viable approaches seem to be (in random order)
* fork libmysqlclient
* convince the MySQL folks to revert their li
Quoting Wichert Akkerman ([EMAIL PROTECTED]):
> Previously Marek Habersack wrote:
> > What about a case as mine - Pike 7.4 is MPL/GPL/LGPL. How does that look in
> > this situation?
> You might get away with the MPL/LGPL options, but you should probably
> ask for confirmation on debian-legal.
So,
On Sat, Apr 12, 2003 at 09:06:35PM +0200, Wichert Akkerman wrote:
> Previously Steve Langasek wrote:
> > The new libmysqlclient12 package comes from MySQL 4.0. It has been
> > known for some time that the libmysqclient library in MySQL 4.0 would
> > *not* be released under the LGPL: it is GPL only
Previously Marek Habersack wrote:
> What about a case as mine - Pike 7.4 is MPL/GPL/LGPL. How does that look in
> this situation?
You might get away with the MPL/LGPL options, but you should probably
ask for confirmation on debian-legal.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>
On Sat, Apr 12, 2003 at 09:06:35PM +0200, Wichert Akkerman scribbled:
> Previously Steve Langasek wrote:
> > The new libmysqlclient12 package comes from MySQL 4.0. It has been
> > known for some time that the libmysqclient library in MySQL 4.0 would
> > *not* be released under the LGPL: it is GPL
Previously Steve Langasek wrote:
> The new libmysqlclient12 package comes from MySQL 4.0. It has been
> known for some time that the libmysqclient library in MySQL 4.0 would
> *not* be released under the LGPL: it is GPL only. If your package which
> links against libmysqclient is not GPL-compatib
Hello,
On Sat, Apr 12, 2003 at 12:45:45PM +0200, Christian Hammers wrote:
> The shared library of the MySQL database changed its .so-major-version.
> Therefore I changed the package name
> from libmysqlclient10, libmysqlclient10-dev
> to libmysqlclient12, libmysqlcleint-dev (w/o ve
Hello
The shared library of the MySQL database changed its .so-major-version.
Therefore I changed the package name
from libmysqlclient10, libmysqlclient10-dev
to libmysqlclient12, libmysqlcleint-dev (w/o version)
Please rebuild your packages at least once before the next releas
19 matches
Mail list logo
