Can you walk me through that process?
I'm thinking it would be nice to have a "macro" package that selects a
platform, boot format, packages on that platform, etc.
For instance, being able to build a target called
"net5501-asterisk-squashfs"... What are the steps to making this happen?
On 8/19/10 1:19 PM, Kelly Hogan wrote:
I'd be game for helping on this, as a typical port to other platforms is a bit
of manual work.
I currently have a couple scripts that parse the package definition area from the
.config, and then make delta changes to the new tree, but it would be nice to have a
"Inherit" option within menuconfig that would do that automagically.
On Aug 19, 2010, at 2:04 PM, Philip Prindeville wrote:
Hi.
I mentioned a couple of months ago the possibility of making meta-packages that
select a platform and then a superset of packages to put on it, as a way of
pre-packaging appliances as both a hardware platform and commonly selected
software to go with it.
There seemed to be some interest in doing this.
I need to bring up a couple of new platforms anyway (including a Traverse
Technologies 'Geos' board). Anyone have the time to discuss with me what's
involved in doing this?
Thanks,
-Philip
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
