Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Heidelberg <markus.heidelberg@web.de>
To: buildroot@busybox.net
Subject: [Buildroot] User defined packages?
Date: Tue, 31 Mar 2009 21:08:58 +0200	[thread overview]
Message-ID: <200903312108.58755.markus.heidelberg@web.de> (raw)
In-Reply-To: <FD8B1EC7-BDA6-4BF5-9A65-5BF62E054683@cannasoftware.com>

Lloyd Sargent, 31.03.2009:
> As a noob on this list, if there isn't already a way to add user  
> defined packages, could I suggest the following?
> 
> In package/Config.in add the following line:
> 
> source "user_package/Config.in"
> 
> In a new directory named "user_package" have a file called Config.in  
> with the following:
> 
> menu "User Packages"
> source "package/YourUserDefinedPackage/Config.in"

I guess you meant user_package/ here and not package/

> endmenu
> 
> The advantage to this is that it allows users to add to their list of  
> packages without affecting (or in anyway touching) the files within  
> the "package" directory. And it gives noobs such as myself a feeling  
> of security that they aren't messing up something important.

For a real feeling of security you should use a VCS.

I personally don't like the idea of a separate package directory.
Putting them into package/ only touches package/Config.in. You can add a
new 'menu "My Packages"' at the end of the file or wherever if you like,
this doesn't affect the official files much.

Markus

  parent reply	other threads:[~2009-03-31 19:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 14:44 [Buildroot] User defined packages? Lloyd Sargent
2009-03-31 15:32 ` Lloyd Sargent
2009-03-31 19:08 ` Markus Heidelberg [this message]
     [not found]   ` <200903311637.14499.lsargent@txdigital.com>
2009-04-01  0:11     ` Markus Heidelberg
2009-04-01  0:23       ` Lloyd Sargent

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=200903312108.58755.markus.heidelberg@web.de \
    --to=markus.heidelberg@web.de \
    --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