Re: [PATCH] Don't depend on product path for finding the anaconda-runtime package

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jeremy Katz wrote:
---
 scripts/buildinstall |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/scripts/buildinstall b/scripts/buildinstall
index 81ac3e3..339779c 100755
--- a/scripts/buildinstall
+++ b/scripts/buildinstall
@@ -99,7 +99,8 @@ PKGDIR=$DIR/$PRODUCTPATH
 BUILDINSTDIR=`mktemp -d ${TMPDIR:-/tmp}/buildinstall.tree.XXXXXX`
 TREEDIR=`mktemp -d ${TMPDIR:-/tmp}/treedir.XXXXXX`
-BUILDARCH=`rpm -qp --qf "%{ARCH}\n" $PKGDIR/anaconda-runtime-[0-9]* |head -n 1`
+ANACONDARUNTIME=`find $p -name "anaconda-runtime-[0-9]*" |head -n 1`

Would it be plausible to tail -n 1 it instead? I'm sure the compose tools should only pull in one version but given the way some of these resolve dependencies they might pull in two versions (or more) and tail would get the latest -which may or may not have been modified by a third party.

Does that sound plausible? If so, need a patch?

Kind regards,

Jeroen van Meeuwen
-kanarip

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux