1 |
Hi, |
2 |
I have asked in few past emails to the list about catalyst, |
3 |
and finaly started to work with it. I did a lot of coding to overcome |
4 |
problems with it. I created a script that can create spec files and |
5 |
provide catalyst with the files to create stable or unstable trees. |
6 |
I was asked by Peter Stuge what I would change in catalyst. |
7 |
So here are my points: |
8 |
1. improve the entry points for debugging. Sometimes you will need to |
9 |
start from a certain point, when you debug stuff, so this will provide hooks |
10 |
that are easy to use (commandline), and not the locking directory of the stage. |
11 |
2. Solve some bugs or annoying things when working with catalyst, like |
12 |
/usr/src/ is not created, or the glibc locals. |
13 |
3. I already created a auto generator for spec files. This is the most |
14 |
important bit |
15 |
of the auto working of catalyst. It also auto generate stage4.spec. |
16 |
4. take the fear out of the loop, and be agile to changes. |
17 |
5. Documentation, hehe ;-) I really had hard time using this tool. |
18 |
6. Minimal stage for embedded, that will be able to sustain releases |
19 |
and freeze them |
20 |
It should be implemented something like the crossdev tool, but in more |
21 |
robust way. Also |
22 |
using the ROOT= directive. |
23 |
7. Crossdev integration. |
24 |
8. Implement tiny portage tree (alredy implemented), but need to add |
25 |
support for adding |
26 |
packages to it as we go along. This keeps a really minimal subset |
27 |
snapshot. It is really |
28 |
good for small system, or compiling using tmpfs. I now have 8GB of |
29 |
memory just for |
30 |
the compilations. |
31 |
9. auto creation of qemu image or image that implements grub, |
32 |
partitions and few systems, |
33 |
like debugging and compiling system, and the real embedded system. |
34 |
10. sql + web frontend for people that really don't know gentoo. |
35 |
11. Move to Ruby ;-) (but this is just a dream) |
36 |
12. Make the code functional like C code, and no just big lump of |
37 |
script (mostly in the Bash |
38 |
scripts.) |
39 |
13. It does look like this tool has grown from patch to patch under |
40 |
fire (no time), so it needs |
41 |
some change in the code, to be more understandable. |
42 |
|
43 |
What I consider to do, is create a new catalyst tree, that will serve |
44 |
as "next" tree for catalyst |
45 |
stable. Though I'm still not sure that I'll hold myself not to |
46 |
reorganize everything. |
47 |
I understand that when Gentoo will have a good catalyst for users, |
48 |
this will ease the work |
49 |
of a lot of people, needing to use Gentoo in automated environments. |
50 |
I also tried Metro, but found catalyst to work, and had hard time with Metro. |
51 |
One needs to acknowledge that catalyst holds a lot of pearls in the |
52 |
code, and this is its power. |
53 |
|
54 |
My thoughts, |
55 |
Kfir |