1 |
I know it's a bit late for this discussion, but I never really |
2 |
understood why GLIS wasn't a viable installer project for gentoo. It |
3 |
even seems to me that an initial goal of GLI is to get to the point |
4 |
where GLIS is at right now, i.e. working, based on a configuration file, |
5 |
and highly flexible. GLIS is written in bash and made up of about 8 |
6 |
small bash scripts (except for the partition code, which is way too big |
7 |
for bash), and in my opinion this is really all you need for a gentoo |
8 |
installer since all it takes to install gentoo is a few bash commands. |
9 |
GLIS simply takes those commands and puts them into scripts. |
10 |
|
11 |
I don't think GLIS is the do-all/end-all of installer projects, but I do |
12 |
think it's a good project and that it does the job quite well. I've even |
13 |
written a small gentoo kickstart howto with glis (needs updating) that's |
14 |
posted on the forums. |
15 |
|
16 |
I've followed this installer project from its beginning in January, but |
17 |
it seems like most of core developer's don't have as much spare time to |
18 |
devote to the project as they may have initially thought. If you adopted |
19 |
GLIS as gentoo's installer right now then at least gentoo would have |
20 |
something, and in 6-12 months when GLI is done you could switch over it. |
21 |
The one large development benefit I see from this is that people can |
22 |
immediately start working on a GUI for the installer, and as long as the |
23 |
GUI's interaction with the backend is well enough seperated from its UI, |
24 |
there would be little difficulty in porting the code to work with GLI. |
25 |
|
26 |
Of course having two different installer's at the same time would mean |
27 |
more to manage, but the number of bugs that get reported on GLIS have |
28 |
been very minimal in the past few months and I could easily maintain it |
29 |
myself. |
30 |
|
31 |
Cheers! |
32 |
Scott |
33 |
|
34 |
-- |
35 |
gentoo-installer@g.o mailing list |