From: Nivedita Singhvi <niv@us.ibm.com>
To: Jeremy Katz <katzj@redhat.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] tools: Fix network-bridge to work withGentoo (version 2)
Date: Wed, 05 Oct 2005 13:55:38 -0700 [thread overview]
Message-ID: <43443DCA.4080200@us.ibm.com> (raw)
In-Reply-To: <1128545051.21137.61.camel@bree.local.net>
Jeremy Katz wrote:
> On Wed, 2005-10-05 at 21:25 +0100, Ian Pratt wrote:
>
>>>Thinking aloud -- maybe just setting a variable so we know
>>>we're in the 'make dist' case and using that to install all
>>>the distro specific stuff into DESTDIR and then letting
>>>install.sh also pick out the right distro would work. Then
>>>for the more normal install case, just the proper things for
>>>the distro would get installed. Does this seem reasonable?
>>>I'll try to cook up something today
>>
>>This would be great, but does have the danger that we end up having a
>>swathe of very similar scripts that have to be maintained together.
>
>
> Yeah, this is the downside. After spending a while earlier looking for
> how other projects handle it, it looks like most have gone the route of
> "don't provide anything at all and then distros ship their own". Which
> kind of sucks. :/ It's much like the current problem of not having the
> packaging scripts for each distro.
>
> The only exception tend to be a few projects which detect your
> distribution at configure time and then install an appropriate
> "backend".
We've been thinking a bit about this too, and I think honestly
it won't be that bad - once we have stuff working (and allow distros
to maintain their separate segments), there won't be that much
churn in the underlying xen scripts. Your approach above is
what we'd like to have.
>>It was annoying that gentoo chose not to use ifup/down. I guess with the
>>various udev/hotplug versions we'll need vendor-specific ways of
>>addressing them too.
>
>
> Yep, I'm having to run with Chris Bainbridge's udev rules (with a few
> minor tweaks) since Fedora devel is very current udev as the hotplug
> handler. That's what really got me thinking down this path.
thanks,
Nivedita
next prev parent reply other threads:[~2005-10-05 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 20:25 [PATCH] tools: Fix network-bridge to work withGentoo (version 2) Ian Pratt
2005-10-05 20:44 ` Jeremy Katz
2005-10-05 20:55 ` Nivedita Singhvi [this message]
2005-10-06 10:44 ` Chris Bainbridge
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=43443DCA.4080200@us.ibm.com \
--to=niv@us.ibm.com \
--cc=katzj@redhat.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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.