From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Bluez build system
Date: Wed, 19 Dec 2007 00:30:02 +0100 [thread overview]
Message-ID: <1198020602.8050.208.camel@aeonflux> (raw)
In-Reply-To: <20071218233930.2d96a897@neutrino.cosmos.net>
Hi Didier,
> I just see your autogen.sh and I think about autoreconf. This tool can
> rebuild the autotools in a project like your autogen.sh does.
>
> My project's autogen.sh contains only one line : autoreconf -f
try it on a bare repository from CVS and you will see it fails. It is
not meant for bootstrapping things. And to be quite honest, if it works
for you, you have too many files in your repository that could be
auto-generated.
Regards
Marcel
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-12-18 23:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8a8adccc0709020615m38389d6axe49041f8fbe18c4b@mail.gmail.com>
[not found] ` <1188768824.24968.9.camel@violet>
2007-12-16 20:46 ` [PATCH] Bluez build system Jaap A. Haitsma
2007-12-16 21:49 ` [Bluez-devel] " Marcel Holtmann
2007-12-16 22:49 ` Jaap A. Haitsma
2007-12-17 1:00 ` [Bluez-devel] " Marcel Holtmann
2007-12-17 6:52 ` Jaap A. Haitsma
2007-12-17 19:06 ` [Bluez-devel] " Marcel Holtmann
2007-12-18 22:17 ` Jaap A. Haitsma
2007-12-18 22:39 ` [Bluez-devel] " Didier Link
2007-12-18 23:30 ` Marcel Holtmann [this message]
2007-12-18 23:28 ` 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=1198020602.8050.208.camel@aeonflux \
--to=marcel@holtmann.org \
--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;
as well as URLs for NNTP newsgroup(s).