David Cantrell wrote:
On Sun, 20 Jan 2008 22:30:32 -0500
Jesse Keating <jkeating@xxxxxxxxxx> wrote:
On Mon, 21 Jan 2008 12:04:34 +0900
John Summerfield <debian@xxxxxxxxxxxxxxxxxxxxxx> wrote:
That's what you said last time. I still don't comprehend.
*shrug* Perhaps one of the anaconda developers can chime in with more
details, but it is what it is. If you don't run it on the arch, you
don't get all the right modules in the initrd and various other
problems.
upd-instroot runs yum on the target architecture to set up the root tree that we pull files from to build the stage1 and stage2 images.
Also, we exec the dynamic linker to collect shared libraries we depend on since that stuff tends to change from time to time as things grow and shrink their dependencies. See get_dso_deps() in buildinstall.functions.
Thanks David.
We're making process, but pardon me if I ask "why?" again. I can
understand that someone might have chosen to implement that way, but is
this choice necessary? Could binaries running on Intellish hardware not
do the needed work?
If not, could not that part be done as a preparatory step, after
building everything and putting the repo into shape?
I have in mind that I might, one day, like to hack on an install ISO for
Power (or zSeries or anything else) without having Linux on the target
platform, and if I do have Linux, it could be Debian or Gentoo or
something different again.
I'm pretty confident that I could open an ISO and add a ks file or
another driver and pack it up again (I've done something like that)
without going through the whole build process.
--
Cheers
John
-- spambait
1aaaaaaa@xxxxxxxxxxxxxxxx Z1aaaaaaa@xxxxxxxxxxxxxxxx
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
