From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH 0/3] add --confdir option to configure
Date: Mon, 19 Mar 2012 17:13:22 +0100 [thread overview]
Message-ID: <4F675B22.5080604@redhat.com> (raw)
In-Reply-To: <20120319154319.GF9375@otherpad.lan.raisama.net>
Il 19/03/2012 16:43, Eduardo Habkost ha scritto:
> > No, I'm not suggesting --package-name, I'm suggesting that qemu-kvm
> > would carry a patch to configure that changed a fixed PACKAGE_NAME
> > define.
>
> Are you really suggesting that forcing downstream to carry a patch is
> better than having a configure option?
Not downstream as in RHEL; downstream as in qemu-kvm which is a fork anyway.
> If you suggest making it configurable using a variable on the 'make'
> command-line it would be OK, but I kind of hoped that no modern software
> project would ever require packagers to use configure-by-sed methods to
> set build parameters.
I think the package name is a pretty special case. Even with autotools,
it's pretty much the only thing that requires configure-by-sed to change it.
Paolo
next prev parent reply other threads:[~2012-03-19 16:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 14:47 [Qemu-devel] [PATCH 0/3] add --confdir option to configure Eduardo Habkost
2012-03-19 14:47 ` [Qemu-devel] [PATCH 1/3] Makefile: use $(confdir) instead of hardcoding $(sysconfdir)/qemu Eduardo Habkost
2012-03-19 14:47 ` [Qemu-devel] [PATCH 2/3] qemu-options.hx: refer to confdir instead of sysconfdir on docs Eduardo Habkost
2012-03-19 14:47 ` [Qemu-devel] [PATCH 3/3] configure: make full config dir path configurable Eduardo Habkost
2012-03-19 15:13 ` Anthony Liguori
2012-03-19 15:40 ` Paolo Bonzini
2012-03-19 15:14 ` [Qemu-devel] [PATCH 0/3] add --confdir option to configure Anthony Liguori
2012-03-19 15:31 ` Eduardo Habkost
2012-03-19 15:34 ` Anthony Liguori
2012-03-19 15:43 ` Eduardo Habkost
2012-03-19 15:59 ` Anthony Liguori
2012-03-19 16:09 ` Eduardo Habkost
2012-03-19 16:03 ` Eric Blake
2012-03-19 16:25 ` Anthony Liguori
2012-03-19 16:13 ` Paolo Bonzini [this message]
2012-03-19 16:20 ` Eduardo Habkost
2012-03-19 16:22 ` Anthony Liguori
2012-03-19 16:50 ` Eduardo Habkost
2012-03-19 16:31 ` Paolo Bonzini
2012-03-19 17:02 ` Eduardo Habkost
2012-03-19 16:32 ` Anthony Liguori
2012-03-19 16:34 ` Paolo Bonzini
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=4F675B22.5080604@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.