Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Andersen <andersen@codepoet.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add local directory for non-public packages
Date: Tue, 23 Jan 2007 17:11:04 -0700	[thread overview]
Message-ID: <20070124001104.GB17761@codepoet.org> (raw)
In-Reply-To: <1169593120.5361.17.camel@elrond.sweden.atmel.com>

On Tue Jan 23, 2007 at 11:58:40PM +0100, Ulf Samuelsson wrote:
> This adds a "buildroot/local" directory.
> The structure of "local" is the same as that of "packages"
> but the contents of "local" is never
> intended to be merged upstream.
> 
> It allows simple maintenance of those application
> since you only need to move the local directory from
> one version of buildroot to a newer.
> 
> Best Regards
> Ulf Samuelsson

See package/customize/ which tries to do the same thing.

If you think perhaps package/customize/ should be renamed
or better documented I'm open to that.  Adding a second
directory doing the same thing however seems unwise.


 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

  reply	other threads:[~2007-01-24  0:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23 22:58 [Buildroot] [PATCH] Add local directory for non-public packages Ulf Samuelsson
2007-01-24  0:11 ` Erik Andersen [this message]
2007-01-24  1:13   ` Ulf Samuelsson
2007-01-24  9:17     ` Thomas Lundquist
2007-01-24 11:58     ` Daniel Laird
2007-01-24 12:11       ` Ulf Samuelsson
2007-01-24 11:37   ` Daniel Laird
2007-01-24 15:02     ` Ulf Samuelsson
2007-01-24 20:29       ` Lars Munch
2007-01-24 21:35         ` Ulf Samuelsson
2007-01-25 12:59           ` iks hefem
2007-01-26 16:18     ` MikeW

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=20070124001104.GB17761@codepoet.org \
    --to=andersen@codepoet.org \
    --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