From: Edd Dumbill <edd@usefulinc.com>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] libtool and autoconf versions
Date: Sun, 18 Jan 2004 11:11:22 +0000 [thread overview]
Message-ID: <1074424282.16573.52.camel@saag> (raw)
The BlueZ packages still use libtool1.4 and autoconf2.13, which are
outdated.
Debian wants to remove support for libtool1.4. The reasons for the
dropping of libtool1.4 are here:
http://lists.debian.org/debian-devel/2004/debian-devel-200401/msg00968.html
What do you think to the idea of updating to libtool1.5 and autoconf2.5
(and a newer automake too)?
It's not actually critical right now, as I am not likely to need to
re-run autoconf or libtool to package BlueZ, but it seems likely that
it's a good idea to move to more updated versions of these tools.
-- Edd
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-01-18 11:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 11:11 Edd Dumbill [this message]
2004-01-20 21:02 ` [Bluez-devel] libtool and autoconf versions Max Krasnyansky
2004-01-20 21:05 ` Edd Dumbill
2004-01-20 21:10 ` Max Krasnyansky
2004-01-21 1:53 ` Marcel Holtmann
2004-01-21 2:07 ` Edd Dumbill
2004-01-21 2:10 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1074424282.16573.52.camel@saag \
--to=edd@usefulinc.com \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox