Perhaps this is by design: the "build tools" dependencies
(anaconda-runtime an friends) which end up in stage2 AFAICS need to be
listed (and their dependencies met) in the main packages listing in
the kickstart file.

Is there a way to control those package listings separately? As a
(trivial) example, we end up with an anaconda-runtime rpm in the iso,
which we are not interested in...

cheers,



m
-- 
 [EMAIL PROTECTED]
 [EMAIL PROTECTED] -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff

--
Fedora-buildsys-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

Reply via email to