From: Cristi Magherusan <Cristi.Magherusan@net.utcluj.ro>
To: buildroot@busybox.net
Subject: [Buildroot] [Patch] OpenVZ tools
Date: Thu, 02 Jul 2009 16:18:21 +0300 [thread overview]
Message-ID: <1246540701.31666.106.camel@localhost.localdomain> (raw)
In-Reply-To: <20090619101249.GB9260@zelow.no>
On Fri, 2009-06-19 at 12:12 +0200, Thomas Lundquist wrote:
> On Mon, Jun 15, 2009 at 11:29:35PM +0300, Cristi Magherusan wrote:
> >
> > By the way, wouldn't it be nicer to have a devlists.sh file which would
> > contain "if" clauses in order to create devices according to the
> > configuration, and the file could be executed to create the real devlist
> > file. This way we could ensure the device needed by a tool is there, and
> > missing when the tool is not compiled.
>
> I'd rather have the devices needed contained either in the package
> makefile or a configuration file in the package directory.
>
> if(defs) like you suggest would soon become a mess.
I admit this.
Then we could enhance the build system so that the package directories
contain devlist.txt files that may be used along with the main device
list file.
Is this acceptable?
Regards,
Cristi
--
Ing. Cristi M?gheru?an, System/Network Engineer
Technical University of Cluj-Napoca, Romania
http://cc.utcluj.ro +40264 401247
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090702/6d7482a3/attachment.pgp>
prev parent reply other threads:[~2009-07-02 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 20:29 [Buildroot] [Patch] OpenVZ tools Cristi Magherusan
2009-06-19 10:12 ` Thomas Lundquist
2009-07-02 13:18 ` Cristi Magherusan [this message]
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=1246540701.31666.106.camel@localhost.localdomain \
--to=cristi.magherusan@net.utcluj.ro \
--cc=buildroot@busybox.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