Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nathanael D. Noblet <nathanael@gnat.ca>
To: buildroot@busybox.net
Subject: [Buildroot] Suggestion, Keep version in a separate file.
Date: Mon, 06 Nov 2006 14:29:31 -0700	[thread overview]
Message-ID: <1162848571.7568.21.camel@iridium.gnat.ca> (raw)
In-Reply-To: <LS3rmy351Zd4.Fk5h2M9g@mailout.dof.se>

On Mon, 2006-11-06 at 22:29 +0200, Ulf Samuelsson wrote:
> I believe it would be a good
> idea to separate the version
> info and download site 
> from the <package>.mk.
> and keep a central file
> with this info.
> 
> This would make it easier
> to handle several projects
> using different versions
> of packages with the same
> framework.
> As part of this I think patches
> to packages should reside
> in a subdirectory to the
> main package directory.

Though I don't know if the implementation idea is the same, I would
*love* a system that allows me to build multiple root fs, and keep the
versions of all packages etc. so that I can reproduce it at will and/or
upgrade a package version for only one target. I started working on
something similar to what you are suggesting, but then my RAID 5 array
had 1 drive die, and bad blocks on the second grrrr so I've lost all
that I had done. I would be interested in helping. I think the main
point to success for something like this is that without any work on
everyone elses part buildroot needs to continue to function as it does
now for the most part, but those of us that want to be able to use it as
you describe could, without much difficulty.
-- 
Nathanael D. Noblet <nathanael@gnat.ca>
Gnat Solutions, Inc

  parent reply	other threads:[~2006-11-06 21:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 20:29 [Buildroot] Suggestion, Keep version in a separate file Ulf Samuelsson
2006-11-06 21:13 ` Marc Lindahl
2006-11-06 21:29 ` Nathanael D. Noblet [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-07  7:43 Ulf Samuelsson
2006-11-07 16:53 ` Marc Lindahl
2006-11-07 21:10   ` Ulf Samuelsson
2006-11-14 21:00     ` Marc Lindahl

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=1162848571.7568.21.camel@iridium.gnat.ca \
    --to=nathanael@gnat.ca \
    --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