From: "Sean" <seanlkml@sympatico.ca>
To: "Peter Williams" <pwil3058@bigpond.net.au>
Cc: git@vger.kernel.org
Subject: Re: Strange dependency problem installing GIT 0.99.7
Date: Mon, 19 Sep 2005 03:16:31 -0400 (EDT) [thread overview]
Message-ID: <BAYC1-PASMTP01B5899CE20655464E3DDFAE920@CEZ.ICE> (raw)
Message-ID: <40363.10.10.10.28.1127114191.squirrel@linux1> (raw)
In-Reply-To: <432E598A.7020306@bigpond.net.au>
On Mon, September 19, 2005 2:24 am, Peter Williams said:
> IMHO rpm shouldn't care how ShellQuote got there unless it (how it got
> there) is stated as an explicit dependency in the spec file (which it
> isn't). So I still think this is a bug in rpm's (automatic) dependency
> mechanism that needs fixing.
But rpm resolves dependencies by looking in the rpm database not by
checking the filesystem. You can actually disable the automatic perl
dependency detection when creating the rpm, but that probably isn't
desirable.
At least on Red Hat/Fedora machines you can create your own rpms directly
from CPAN so it's not too big a restriction:
$ cpan2rpm String::ShellQuote
$ cd ~/rpm/RPMS/noarch
$ sudo rpm -ivh perl-String-ShellQuote-1.03-1.noarch.rpm
Which is all you need to download, package and install the perl module.
> PS I notice that perl isn't included in the explicit list of
> dependencies in the spec file even though other equally ubiquitous
> packages are.
There is special handling for perl detection within the rpmbuild
procedure, so perl will be added automatically where many others won't be.
Sean
next prev parent reply other threads:[~2005-09-19 7:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 2:15 Strange dependency problem installing GIT 0.99.7 Peter Williams
2005-09-19 4:46 ` Junio C Hamano
2005-09-19 5:11 ` Peter Williams
2005-09-19 5:17 ` Sean
2005-09-19 6:24 ` Peter Williams
[not found] ` <40363.10.10.10.28.1127114191.squirrel@linux1>
2005-09-19 7:16 ` Sean [this message]
2005-09-19 19:23 ` H. Peter Anvin
2005-09-19 22:06 ` Horst von Brand
[not found] ` <57460.10.10.10.28.1127110444.squirrel@linux1>
2005-09-19 6:14 ` Sean
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=BAYC1-PASMTP01B5899CE20655464E3DDFAE920@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--cc=git@vger.kernel.org \
--cc=pwil3058@bigpond.net.au \
/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;
as well as URLs for NNTP newsgroup(s).