From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: How to avoid spurious RPM dependencies?
Date: Tue, 17 Jan 2012 14:50:22 -0600 [thread overview]
Message-ID: <4F15DF0E.4090100@windriver.com> (raw)
In-Reply-To: <0AB83639-9F7B-450B-9F50-5D1951F2F5C2@dominion.thruhere.net>
On 1/17/12 2:14 PM, Koen Kooi wrote:
> Hi,
>
> I'm running into a problem with vim that seems to be caused by overeager rpmdeps:
>
> | error: Failed dependencies:
> | /bin/csh is needed by vim-7.2.446-r10.3.armv7a
> | /usr/local/bin/python is needed by python-imaging-1.1.7-r0.armv7a
>
> For vim I thing it's being caused by this:
The dependency scanner checks that a file is executable before scanning it.
> ./usr/share/vim/vim72/tools/vim132:1:#!/bin/csh
>
> What's the best way to stop rpm from wanting csh? Python-imaging is actually broken:
So in the csh case, if it's an example and not something people would normally
be executing simply remove the execute bit -- otherwise it's bug and should be
addressed in some way. (My preference when I see csh scripts is to execute an
rm -f) ;)
> ./usr/bin/pilfile.py:1:#! /usr/local/bin/python
> ./usr/bin/pilprint.py:1:#! /usr/local/bin/python
> ./usr/bin/pilconvert.py:1:#! /usr/local/bin/python
>
> Is #!/usr/bin/env python still the preferred shebang?
Yes, that is the preferred way of referring to python.
--Mark
> regards,
>
> Koen
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2012-01-17 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 20:14 How to avoid spurious RPM dependencies? Koen Kooi
2012-01-17 20:41 ` McClintock Matthew-B29882
2012-01-17 20:50 ` 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=4F15DF0E.4090100@windriver.com \
--to=mark.hatle@windriver.com \
--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