From: Petr Baudis <pasky@suse.cz>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Junio C Hamano <junkio@cox.net>,
Josef Weidendorfer <Josef.Weidendorfer@gmx.de>,
git@vger.kernel.org
Subject: Re: [PATCH] Small script to patch .spec for Suse
Date: Tue, 15 Nov 2005 22:59:43 +0100 [thread overview]
Message-ID: <20051115215943.GW30496@pasky.or.cz> (raw)
In-Reply-To: <437A46E4.5010909@zytor.com>
Dear diary, on Tue, Nov 15, 2005 at 09:36:52PM CET, I got a letter
where "H. Peter Anvin" <hpa@zytor.com> said that...
> Junio C Hamano wrote:
> >
> >I've applied the patch from HPA to update it to git.spec already
> >in my tree, so your script would not work any more ;-)
> >
> >But seriously, I suspect we should take a hint from the fact
> >that "git.spec.in" has ".in" in its name already.
> >
>
> 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.
Actually, can you have some kind of %if in specfiles? Then you could
keep everything in the specfile and just pass it whatever system you
want to build for.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
next prev parent reply other threads:[~2005-11-15 21:59 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
2005-11-15 21:59 ` Petr Baudis [this message]
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=20051115215943.GW30496@pasky.or.cz \
--to=pasky@suse.cz \
--cc=Josef.Weidendorfer@gmx.de \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--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).