Add local directory for non-public packages
PATCH 1/1 Add local directory for non-public packages
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Makefile_local.patch
Type: text/x-patch
Size: 1458 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20070123/74be3a88/attachment-0001.bin
PATCH 1/1 Add local directory for non-public packages
Quoted 11 lines · Ulf Samuelsson
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--
PATCH 1/1 Add local directory for non-public packages
Quoted 6 lines · Erik Andersen
Quoted 5 lines · Ulf Samuelsson
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.
Quoted 9 lines
Quoted 6 lines
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 SamuelssonSee package/customize/ which tries to do the same thing.
Package "customize" *copies* things into the file system I think this is useful if you want to have things like web pages into the root system.
"local" is for "building" packages which should be in the file system, but may be of a prorprietary nature, or for testing purpose or whatever.
The purpose is mainly easy maintenance. Anything in local could be in "packages", but since it is never going into the mainstream,
so you have to update those packages every time you update the buildroot.
By definition, this is the only patch for "local" there will ever be. Anything going into mainstream buildroot should go into "packages"
Quoted 6 lines
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
Best Regards,
Ulf Samuelsson
ulf at atmel.com
GSM: +46 (706) 22 44 57
Tel: +46 (8) 441 54 22
Fax: +46 (8) 441 54 29
Mail: Box 2033 174 02 Sundbyberg
Visit: Kavalleriv?gen 24
174 58 Sundbyberg'Sweden
PATCH 1/1 Add local directory for non-public packages
Quoted 3 lines · Ulf Samuelsson
"local" is for "building" packages which should be in the file system, but may be of a prorprietary nature, or for testing purpose or whatever.
I'd be very happy if this patch was included.
Thomas.
PATCH 1/1 Add local directory for non-public packages
In reply to Ulf SamuelssonDo you need to patch the top level Config.in to include local/Config.in? I think this is needed for the menuconfig stuff.
Cheers
Dan
Signature · 2 lines
View this message in context: http://www.nabble.com/-PATCH--Add-local-directory-for-non-public-packages-tf3078310.html#a8559127 Sent from the BuildRoot mailing list archive at Nabble.com.
PATCH 1/1 Add local directory for non-public packages
Quoted 2 lines · Daniel Laird
Do you need to patch the top level Config.in to include local/Config.in? I think this is needed for the menuconfig stuff.
True.
Quoted 3 lines
Cheers
Dan
Best Regards,
Ulf Samuelsson
ulf at atmel.com
GSM: +46 (706) 22 44 57
Tel: +46 (8) 441 54 22
Fax: +46 (8) 441 54 29
Mail: Box 2033 174 02 Sundbyberg
Visit: Kavalleriv?gen 24
174 58 Sundbyberg'Sweden
PATCH 1/1 Add local directory for non-public packages
In reply to Erik AndersenQuoted 23 lines · Erik Andersen
Quoted 11 lines · Ulf Samuelsson
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 SamuelssonSee 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
Quoted 9 lines
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
_______________________________________________
buildroot mailing list
buildroot at uclibc.org
http://busybox.net/mailman/listinfo/buildroot
I too would be very happy to see this patch go in. It means buildroot can be a more generic build system allowing people to easily move from version to version. But also allows people to use it to build their own packages that are not going to be ever part of the open-source world, or are so specialised as to be of limited use to the main buildroot community. Dan
Signature · 2 lines
View this message in context: http://www.nabble.com/-PATCH--Add-local-directory-for-non-public-packages-tf3078310.html#a8558857 Sent from the BuildRoot mailing list archive at Nabble.com.
PATCH 1/1 Add local directory for non-public packages
ons 2007-01-24 klockan 03:37 -0800 skrev Daniel Laird:
Quoted 35 lines
Quoted 23 lines · Erik Andersen
Quoted 11 lines · Ulf Samuelsson
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 SamuelssonSee 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
Quoted 9 lines
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
_______________________________________________
buildroot mailing list
buildroot at uclibc.org
http://busybox.net/mailman/listinfo/buildroot
Quoted 6 lines
I too would be very happy to see this patch go in. It means buildroot can be a more generic build system allowing people to easily move from version to version. But also allows people to use it to build their own packages that are not going to be ever part of the open-source world, or are so specialised as to be of limited use to the main buildroot community. Dan
Here is an updated patch which includes the local/Config.in. As I explained in the previous Email, the "package/customize" and "local" have two distinct functions.
If you move up "buildroot/package/customize" to "buildroot/customize" and make the "Config.in" and "customize.mk" empty,
then that would be ok as well.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Makefile_local.patch
Type: text/x-patch
Size: 1771 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20070124/25349706/attachment.bin
PATCH 1/1 Add local directory for non-public packages
Hi Ulf
Quoted 6 lines · Ulf Samuelsson
Here is an updated patch which includes the local/Config.in. As I explained in the previous Email, the "package/customize" and "local" have two distinct functions.
If you move up "buildroot/package/customize" to "buildroot/customize" and make the "Config.in" and "customize.mk" empty,
then that would be ok as well.
[snip]
I really like this idea of having a directory for "local" packages, but I think it would be nice to take it a step further and make it possible to set the directory where the "local" packages are located. Then it will be possible to have your "local" packages out of the buildroot tree.
Just my 2 cent.
-- Lars Munch
PATCH 1/1 Add local directory for non-public packages
Quoted 9 lines · Lars Munch
Hi Ulf
Quoted 6 lines · Ulf Samuelsson
Here is an updated patch which includes the local/Config.in. As I explained in the previous Email, the "package/customize" and "local" have two distinct functions.
If you move up "buildroot/package/customize" to "buildroot/customize" and make the "Config.in" and "customize.mk" empty,
then that would be ok as well.
Quoted 8 lines
[snip]
I really like this idea of having a directory for "local" packages, but I think it would be nice to take it a step further and make it possible to set the directory where the "local" packages are located. Then it will be possible to have your "local" packages out of the buildroot tree.
Not a bad idea!
Quoted 3 lines
Just my 2 cent.
-- Lars Munch
Best Regards,
Ulf Samuelsson
PATCH 1/1 Add local directory for non-public packages
+1 for me
Quoted 6 lines
Quoted 3 lines
Then it will be possible to have your "local" packages out of the buildroot tree.
Not a bad idea!
PATCH 1/1 Add local directory for non-public packages
In reply to Daniel LairdQuoted 7 lines · Daniel Laird
I too would be very happy to see this patch go in. It means buildroot can be a more generic build system allowing people to easily move from version to version. But also allows people to use it to build their own packages that are not going to be ever part of the open-source world, or are so specialised as to be of limited use to the main buildroot community. Dan
All that's missing now is a menuconfig option to allow use of an external toolchain ...
Cheers,
MikeW
PS hi to 225/810 guys Dan !