On Aug 27, 2009, at 13:57, David Cantrell <dcantrell@xxxxxxxxxx> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 27 Aug 2009, Jesse Keating wrote:
On Aug 27, 2009, at 13:27, Chris Lumens <clumens@xxxxxxxxxx> wrote:
If you are working on the buildinstall scripts, you can pass the
--localscripts option to buildinstall to force it to use the
scripts
from the current directory rather than downloading the anaconda RPM
from the repo you specify, unpacking it, and using the scripts from
there.
---
scripts/buildinstall | 75 ++++++++++++++++++++++++++++
+--------------------
1 files changed, 44 insertions(+), 31 deletions(-)
Great idea.
Isn't this the same as pointing --updates at the working dir?
Probably, but the way buildinstall works is still part black magic
to me. I
wanted something to skip the whole finding anaconda, unpacking it,
and using
scripts from there. I don't have an updated anaconda RPM that I
could point
to anyway, nor did I want to make one.
--updates doesn't take a new rpm, it takes a path that has updated
scripts. I'll look a the patch again and maybe collapse the
functionality so that both your new option and --updates uses the same
code paths. There is already enough magic going on here.
--
Jes
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
