| 1 |
> Now, can we get to the backend already? |
| 2 |
|
| 3 |
Well what made the frontend so easy was that it's just a mock-up that |
| 4 |
uses a hard-coded list of packages and generally doesn't care about |
| 5 |
reality :). |
| 6 |
|
| 7 |
As for backend, the idea came to me recently to make this entirely |
| 8 |
modular - have certain tasks defined that must be provided by each |
| 9 |
module (I'd be writing the gentoo-embedded module and hopefully also |
| 10 |
the gentoo-standard/gentoo-desktop module). For instance, each module |
| 11 |
would need to provide a function that provided a (categorized) list of |
| 12 |
available packages for the front-end, and a function for the backend |
| 13 |
that would install a given package. There could also be distribution |
| 14 |
modules, one for tar-gz, one for tar-bz2, and a more complicated one |
| 15 |
to set up a bootable ISO. |
| 16 |
|
| 17 |
That would make this project better coded by separating |
| 18 |
Gentoo-specific stuff (which will need to be updated as Portage |
| 19 |
continues to have changes made to it) from stuff that's really |
| 20 |
Gentoo-independent, and it will also make it much simpler once I |
| 21 |
finish the first run through with the embedded work to add another |
| 22 |
module that will generate install scripts and such to help along |
| 23 |
desktop users with their installation. Also, should another distro |
| 24 |
want to make use of this, it would make it far easier to use - you |
| 25 |
could just write a new module and tweak the main project as needed |
| 26 |
instead of gutting it and replacing all the Gentoo parts. |
Archives