From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Andreas Ericsson <ae@op5.se>,
git@vger.kernel.org, Chris Wright <chrisw@osdl.org>
Subject: Re: git-core-arch: Missing dependency
Date: Fri, 11 Nov 2005 17:08:19 -0800 [thread overview]
Message-ID: <43754083.4090501@zytor.com> (raw)
In-Reply-To: <7vu0ejm30l.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Andreas Ericsson <ae@op5.se> writes:
>
>
>>Junio C Hamano wrote:
>>
>>>Horst von Brand <vonbrand@inf.utfsm.cl> writes:
>>>
>>>
>>>>The command git-archimport makes use of tla, but the relevant package(s) are
>>>>not on the requirements
>>>
>>>Thanks. Should the fix be like this?
>>> Group: Development/Tools
>>>-Requires: git-core = %{version}-%{release}
>>>+Requires: git-core = %{version}-%{release}, tla
>>
>>Just to be anal;
>>Requires doesn't usually include the %release,...
>
>
> Obviously both you and Chris (who did the part you are quoting
> for us) know RPM spec a lot better than I do, and I see two
> experts contradicting with each other. It could have been just
> an oversight, or it might have done deliberately --- I cannot
> judge myself, so I punt here. I'll remove "-%{release}" when I
> hear Chris says he agrees with you.
>
You can do it either way. It's a matter of the strictness of the
binding. If you put %{version} there, then it has to come from the same
upstream release; for %{version}-%{release} it has to come from the same
SRPM, i.e. usually from the same build.
In this case I think %{version}-%{release} is appropriate.
-hpa
next prev parent reply other threads:[~2005-11-12 1:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 14:46 git-core-arch: Missing dependency Horst von Brand
2005-11-11 17:33 ` Junio C Hamano
2005-11-11 18:20 ` Andreas Ericsson
2005-11-11 18:51 ` Junio C Hamano
2005-11-12 1:08 ` H. Peter Anvin [this message]
2005-11-12 1:26 ` Chris Wright
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=43754083.4090501@zytor.com \
--to=hpa@zytor.com \
--cc=ae@op5.se \
--cc=chrisw@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).