Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140427212441.GB3571@openwall.com>
Date: Mon, 28 Apr 2014 01:24:41 +0400
From: croco@...nwall.com
To: owl-dev@...ts.openwall.com
Subject: Re: trying to build Owl for Raspberry Pi: rpmquery
 --specfile

On Sun, Apr 27, 2014 at 04:58:49PM +0400, Dmitry V. Levin wrote:
> 
> rpmquery used to support --specfile option, but in rpm >= 4.9.0
> this functionality was moved to a new tool called rpmspec.
> "rpm --specfile" is aliased there to "rpmspec -q", but
> there is no similar alias for "rpmquery --specfile":
> $ grep -Fe --specfile /usr/lib/rpm/rpmpopt
> rpm	exec --specfile		rpmspec -q
> 
> You can add one and see where the build stops next.

Well, I'm not that familiar with rpm, and as of now I'm totally confused
with the file /usr/lib/rpm/rpmpopt-4.9.1.3 (is this the one I need?)
WHAT (I mean, _which_ "one") should I add, and where?  BTW, the file in
question is commented as "shoud not be modified", and there's a note that
"local changes should go to /etc/popd, not here"; well, there's an empty
directory /etc/popd.d, no other files there and no idea how to deal with
all these mess.

Anyway, in such a situation, may be it could be wiser to patch Owl build
scripts instead of trying to reconfigure rpm?   Depending on a feature
which is known to disappear doesn't look a good idea to me.


Thanks!


--
Croco

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.