From: Marcel Holtmann <marcel@holtmann.org>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: Edd Dumbill <edd@usefulinc.com>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] libtool and autoconf versions
Date: Wed, 21 Jan 2004 02:53:26 +0100 [thread overview]
Message-ID: <1074650005.7088.56.camel@pegasus> (raw)
In-Reply-To: <1074633031.1707.190.camel@localhost>
Hi Edd,
> > I'm talking about what's shipped in the tarballs, which uses
> > libtool1.4. Packagers for distros rely on the tarball releases. In the
> > (admittedly) unlikely event that changes need to be made and autoconf
> > re-run for the purposes of packaging, the old ac and libtool would be
> > needed.
> I see. Yeah, I think we should release our tarballs with new autoconf.
> Marcel, it's time for you to upgrade ;-).
what version of libtool and autoconf is used for Debian Woody? Do Debian
Sarge already uses the new versions?
Regards
Marcel
-------------------------------------------------------
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 prev parent reply other threads:[~2004-01-21 1:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 11:11 [Bluez-devel] libtool and autoconf versions Edd Dumbill
2004-01-20 21:02 ` Max Krasnyansky
2004-01-20 21:05 ` Edd Dumbill
2004-01-20 21:10 ` Max Krasnyansky
2004-01-21 1:53 ` Marcel Holtmann [this message]
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=1074650005.7088.56.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=edd@usefulinc.com \
--cc=maxk@qualcomm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.