Hi! I've just build an ebuild for the ADK (Appliance Development Kit) of FreeWRT, which is a meta GNU/Linux distribution for embedded systems. For further details see the website. http://freewrt.org It is distributed under it’s own FreeWRT license. You can review it at http://freewrt.org/trac/browser/trunk/freewrt/LICENCE I put that ebuild into the dev-util category. I think that’s the one it fits best in. This is now all up to your consideration. PS: You can get this from my overlay as well. http://overlay.anello-net.de/layman.xml Regards Antonino Catinello Reproducible: Always
Created attachment 179470 [details] freewrt-1.0.3.ebuild
Created attachment 179472 [details] metadata.xml
As is, that ebuild is unacceptable. For one thing, it shouldn't depend on all those packages that are part of the system target. On a more major note, it simply downloads stuff and installs it to /usr/src/foo, which isn't exactly what an ebuild should do.
But that's all that ebuild is supposed to do. You can't automate anything more than this. That package contains the source/kit. User configuration is necessary. Look at it as a kernel, because that's basically what it is. A all in one kernel + tools source package. I couldn't find anything like _system target_ packages list with a quick look at the devmanuel. Which packages are not supposed to be in that ebuild? gcc, glibc, patch, flex, make ... of course they are not, the package is still depending on it though. I just added all the prerequisites that are mentioned in the handbook, with current stable versions that worked for myself. See the handbook: http://www.freewrt.org/docs/1.0/handbook/html-single/handbook.html#SECTION00310000000000000000
Created attachment 180290 [details] updated ebuild - docs and removed some dependencies I've removed some dependencies as requested.
Created attachment 182369 [details] fixed dependencies
