From: Andreas Ericsson <ae@op5.se>
To: git@vger.kernel.org
Subject: Re: [PATCH] Small script to patch .spec for Suse
Date: Tue, 15 Nov 2005 22:56:05 +0100 [thread overview]
Message-ID: <437A5975.3020705@op5.se> (raw)
In-Reply-To: <437A46E4.5010909@zytor.com>
H. Peter Anvin wrote:
>
> I'd prefer to have just @@OPENSSH_PACKAGE@@ and @@EXPAT_PACKAGE@@
> instead of completely virtualizing the dependencies. Less flexible to
> be sure, but it makes it less confusing to read and fix.
>
git doesn't, strictly speaking, require openssh, for two reasons;
a. It's been known to work equally well over rsh.
b. ssh is run as an executed command. ssh can be installed later and the
previously installed git will start working just like magic.
If you really *want* an openssh requirement, you should just go with
Requires: /usr/bin/ssh
It's the most accurate one after all, since git doesn't really care
which package it came from so long as it's there.
As for BuildRequires, I think package maintainers can be trusted to
figure those out for themselves. It's not as if they'll be producing
flawed RPM's after all.
If you want one for expat anyways, then go with
BuildRequires: expat
since that's true for both dists (and FC maintainers will then happily
figure out that they need expat-devel to build it).
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2005-11-15 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 11:30 [PATCH] Small script to patch .spec for Suse Josef Weidendorfer
2005-11-15 18:50 ` Junio C Hamano
2005-11-15 20:36 ` H. Peter Anvin
2005-11-15 21:47 ` Junio C Hamano
2005-11-15 21:56 ` Andreas Ericsson [this message]
2005-11-15 21:59 ` Petr Baudis
2005-11-15 22:22 ` H. Peter Anvin
2005-11-16 1:32 ` Josef Weidendorfer
2005-11-18 5:11 ` H. Peter Anvin
2005-11-18 5:47 ` A Large Angry SCM
2005-11-18 5:57 ` H. Peter Anvin
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=437A5975.3020705@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).