From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: is there a way for "rpm -ql" (v5) to *not* print intervening dirs?
Date: Wed, 26 Oct 2016 05:05:08 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1610260501540.17439@ca624034.mitel.com> (raw)
a mundane issue, but i just noticed that rpm5 that comes with OE
insists on printing all intervening directories with "rpm -ql", as in
it would print:
/usr
/usr/lib
/usr/lib/perl
/usr/lib/perl/5.22.1/
/usr/lib/perl/5.22.1/Encode.pm
just to show that that last file is part of a given package. is there
an option to not have it do that, to behave like rpm4 did? thanks.
more perl packaging questions coming shortly ...
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
reply other threads:[~2016-10-26 9:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.20.1610260501540.17439@ca624034.mitel.com \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox