On 03/19/2012 11:20 AM, Eduardo Habkost wrote:
On Mon, Mar 19, 2012 at 05:13:22PM +0100, Paolo Bonzini wrote:
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
d
On 03/19/2012 10:31 AM, Eduardo Habkost wrote:
On Mon, Mar 19, 2012 at 10:14:54AM -0500, Anthony Liguori wrote:
On 03/19/2012 09:47 AM, Eduardo Habkost wrote:
This series change the Makefile to use $(confdir) instead of
$(sysconfdir)/qemu, and allows the full config path configurable instead of
On 03/19/2012 10:43 AM, Eduardo Habkost wrote:
On Mon, Mar 19, 2012 at 10:34:06AM -0500, Anthony Liguori wrote:
On 03/19/2012 10:31 AM, Eduardo Habkost wrote:
On Mon, Mar 19, 2012 at 10:14:54AM -0500, Anthony Liguori wrote:
On 03/19/2012 09:47 AM, Eduardo Habkost wrote:
This series change the
On 03/19/2012 11:20 AM, Eduardo Habkost wrote:
On Mon, Mar 19, 2012 at 05:13:22PM +0100, Paolo Bonzini wrote:
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
d
On 03/19/2012 11:03 AM, Eric Blake wrote:
On 03/19/2012 09:43 AM, Eduardo Habkost wrote:
A --package-name option could be provided to make it easier to override
all the defaults at the same time, but I don't see why not include an
option to define the full path for confdir, just like we allow fo
On 03/19/2012 09:47 AM, Eduardo Habkost wrote:
This series change the Makefile to use $(confdir) instead of
$(sysconfdir)/qemu, and allows the full config path configurable instead of
forcing the use of $(sysconfdir)/qemu.
What's the use case here? Is this to allow $(sysconfdir)/qemu-kvm?
I'd
On Mon, Mar 19, 2012 at 05:31:34PM +0100, Paolo Bonzini wrote:
> Il 19/03/2012 17:20, Eduardo Habkost ha scritto:
> > Anyway, even if we decide that package name shouldn't be changed: why
> > changing mandir,
>
> This one is because all manpages are under /usr/man/manSECT
>
> > docdir and datadir
On Mon, Mar 19, 2012 at 11:22:26AM -0500, Anthony Liguori wrote:
> On 03/19/2012 11:20 AM, Eduardo Habkost wrote:
> >On Mon, Mar 19, 2012 at 05:13:22PM +0100, Paolo Bonzini wrote:
> >>Il 19/03/2012 16:43, Eduardo Habkost ha scritto:
> No, I'm not suggesting --package-name, I'm suggesting that q
Il 19/03/2012 17:32, Anthony Liguori ha scritto:
>> I still don't understand why, except that it's a limitation of the build
>> system implementation. If we don't have that restriction, I don't see
>> why this should be restricted by design.
>>
>> Anyway, even if we decide that package name shouldn
Il 19/03/2012 17:20, Eduardo Habkost ha scritto:
>> > 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.
> I still don't understand why, except that it's a limitation of the build
> system
On Mon, Mar 19, 2012 at 05:13:22PM +0100, Paolo Bonzini wrote:
> 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
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
On Mon, Mar 19, 2012 at 10:59:35AM -0500, Anthony Liguori wrote:
> On 03/19/2012 10:43 AM, Eduardo Habkost wrote:
> >On Mon, Mar 19, 2012 at 10:34:06AM -0500, Anthony Liguori wrote:
> >>On 03/19/2012 10:31 AM, Eduardo Habkost wrote:
> >>>On Mon, Mar 19, 2012 at 10:14:54AM -0500, Anthony Liguori wro
On 03/19/2012 09:43 AM, Eduardo Habkost wrote:
>>> A --package-name option could be provided to make it easier to override
>>> all the defaults at the same time, but I don't see why not include an
>>> option to define the full path for confdir, just like we allow for
>>> datadir, docdir, and mandir
On Mon, Mar 19, 2012 at 10:34:06AM -0500, Anthony Liguori wrote:
> On 03/19/2012 10:31 AM, Eduardo Habkost wrote:
> >On Mon, Mar 19, 2012 at 10:14:54AM -0500, Anthony Liguori wrote:
> >>On 03/19/2012 09:47 AM, Eduardo Habkost wrote:
> >>>This series change the Makefile to use $(confdir) instead of
On Mon, Mar 19, 2012 at 10:14:54AM -0500, Anthony Liguori wrote:
> On 03/19/2012 09:47 AM, Eduardo Habkost wrote:
> >This series change the Makefile to use $(confdir) instead of
> >$(sysconfdir)/qemu, and allows the full config path configurable instead of
> >forcing the use of $(sysconfdir)/qemu.
This series change the Makefile to use $(confdir) instead of
$(sysconfdir)/qemu, and allows the full config path configurable instead of
forcing the use of $(sysconfdir)/qemu.
Eduardo Habkost (3):
Makefile: use $(confdir) instead of hardcoding $(sysconfdir)/qemu
qemu-options.hx: refer to confd
17 matches
Mail list logo
