| 1 |
On Sat, 2006-08-12 at 19:50 -0400, Mike Frysinger wrote: |
| 2 |
> so i was tooling along the road thinking about what it would take for people |
| 3 |
> to sit down and use Gentoo/embedded for the target ... currently we have misc |
| 4 |
> ways of doing this by hand (install mask/etc...), but it tends to be error |
| 5 |
> prone and it requires the end user to know more than they should about the |
| 6 |
> portage environment |
| 7 |
> |
| 8 |
> what would help here is a frontend ... something like uClinux or Open Embedded |
| 9 |
> where a menu system allows the user to select the packages to install into |
| 10 |
> the target image and when they're done, they simply type 'make' ... wait a |
| 11 |
> bit and they're left with images that they can take and flash onto the target |
| 12 |
> board |
| 13 |
> |
| 14 |
> so really, a friendly frontend for the user to select the characteristics of |
| 15 |
> the system, and then a backend to take that config and use emerge to build |
| 16 |
> everything and generate an image ... would make it easy to create stock board |
| 17 |
> descriptions too ... |
| 18 |
> |
| 19 |
> what do you guys think ? stupid idea ? |
| 20 |
|
| 21 |
Not silly.. I'd tie it into (lx)dialog/Xdialog and skip anything to do |
| 22 |
with catalyst as it tends to be cumbersome for embedded use (plus GNAP |
| 23 |
already exists). using the classic dialog method will provide the most |
| 24 |
familiarity to what buildroot users already expect. |
| 25 |
Then again I'm rather also fond of using single meta ebuilds to handle |
| 26 |
everything but that requires calling emerge from within an ebuild. |
| 27 |
|
| 28 |
> good idea waiting for a champion ? |
| 29 |
|
| 30 |
pretty much.. |
| 31 |
|
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
Ned Ludd <solar@g.o> |
| 36 |
Gentoo Linux |
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-embedded@g.o mailing list |
Archives