Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Lindahl <marc@bowery.com>
To: buildroot@busybox.net
Subject: [Buildroot] Suggestion, Keep version in a separate file.
Date: Mon, 6 Nov 2006 16:13:14 -0500	[thread overview]
Message-ID: <e1b81b87c9e7517e2c7b7a077f8b1bba@bowery.com> (raw)
In-Reply-To: <LS3rmy351Zd4.Fk5h2M9g@mailout.dof.se>

That sounds like it would make the buildroot system overly complicated 
for an rare edge case.
You can do that by managing your .config files - many ways to do that 
already....

On Nov 6, 2006, at 3:29 PM, 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.
>
> /Ulf
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2006-11-06 21:13 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 [this message]
2006-11-06 21:29 ` Nathanael D. Noblet
  -- 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=e1b81b87c9e7517e2c7b7a077f8b1bba@bowery.com \
    --to=marc@bowery.com \
    --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