Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: 'Patches and discussions about the oe-core layer'
	<openembedded-core@lists.openembedded.org>
Subject: Re: RPM and libmagic
Date: Mon, 26 Sep 2011 19:36:25 -0400	[thread overview]
Message-ID: <4E810C79.5030801@windriver.com> (raw)
In-Reply-To: <4E810529.2000708@linux.intel.com>

On 9/26/11 7:05 PM, Saul Wold wrote:
> 
> Mark,
> 
> I recently found a problem with RPM and libmagic, specificly the rpmdeps 
> command as it's used in package.bbclass. The issue being that it was not 
> finding the correct magic.mgc file.  I notice that we wrap the other RPM 
> commands, but not rpmdeps.

That is likely a bug.

> Additionally, as I have discovered the wrappers that we have in place 
> currently does not define a MAGIC environment variable to correct the 
> location.

Is the proper variable "MAGIC" or is it's something else?

> I know rpm and friends are an important part of OE packaging, so I 
> wanted to check with you first about the correct location to set this, 
> if we should use the MAGIC or pass a --define '%_rpmfc_magic_path ...' 
> on the command line.

I believe the intention is to pass the _rpmfs_magic_path..  that patch can be
made up of other potential dynamic results.  If the wrapper is building up
_librpm (something like that), then we can use:

%_rpmfc_magic_path %{_rpmlib}/../../share/magic

Note about is ramblings, not actual code.. ;)

> Please advise, I know you are traveling, and I can implement the change 
> once we figure out the correct approach.

Thanks..  if you need to call me +1-612-669-2612.

> Thanks
> 




      reply	other threads:[~2011-09-26 23:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-26 23:05 RPM and libmagic Saul Wold
2011-09-26 23:36 ` Mark Hatle [this message]

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=4E810C79.5030801@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.com \
    /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