Summary: | catalyst could be nice for live-cd creation | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | REdOG <bugzilla> |
Component: | Catalyst | Assignee: | John Davis (zhen) (RETIRED) <zhen> |
Status: | RESOLVED INVALID | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
REdOG
2004-10-04 14:52:00 UTC
It would be nice if catalyst didn't force the use of genkernel... IMHO genkernel sucks. Well, there is no easier way to consistently automate the kernel building process. Genkernel has come a long way, but of course, it still has some bugs. If you don't like it, write some patches for it. It should be possible to build the stage 1,2 and then run make menuconfig; make modules_install; And go from there... Mabe im missing something but I've built quite a share of custom & generic kernels and have only had 1 sucessful run with genkernel. Not to mention how long it takes when livecd-stage2 fails because of genkernel. Then catalyst ceases to be automatic. User intervention is not a good thing for a tool that people expect to be automated. I have built 100+ livecds and genkernel has only failed a handful of times. Seems like portage oughta be able to fill most of the job catalyst is trying to accomplish... ie: ROOT="/var/tmp/livecd-stage2" emerge system the script could rsync stage1 before that command and produce a stage based on make.conf etc etc from the actual stage1 ( like a real install ) instead of makeing spec files. What? Catalyst uses Portage to do all of the building as is. Also, why emerge system? The build process now is quite efficient. Ok well...mabe im ranting...forgive me....genkernel sucks. Yes, you are. |