From: Chris Wright <chrisw@osdl.org>
To: Petr Baudis <pasky@suse.cz>
Cc: Chris Wright <chrisw@osdl.org>, git@vger.kernel.org
Subject: Re: [PATCH] Update cogito.spec.in
Date: Fri, 16 Sep 2005 08:46:31 -0700 [thread overview]
Message-ID: <20050916154631.GJ8041@shell0.pdx.osdl.net> (raw)
In-Reply-To: <20050916110605.GC25169@pasky.or.cz>
* Petr Baudis (pasky@suse.cz) wrote:
> Dear diary, on Fri, Sep 16, 2005 at 08:47:24AM CEST, I got a letter
> where Chris Wright <chrisw@osdl.org> told me that...
> > e0ca49e6c375a68b3e4b3edfff752fef2cf585f6
> > diff --git a/cogito.spec.in b/cogito.spec.in
> > --- a/cogito.spec.in
> > +++ b/cogito.spec.in
> > @@ -1,15 +1,14 @@
> > Name: cogito
> > Version: @@VERSION@@
> > Release: 1
> > -Vendor: Petr Baudis <pasky@suse.cz>
> > Summary: The Cogito Version Control System
> > License: GPL
> > Group: Development/Tools
> > URL: http://kernel.org/pub/software/scm/cogito/
> > Source: http://kernel.org/pub/software/scm/cogito/%{name}-%{version}.tar.gz
> > -BuildRoot: %{_tmppath}/%{name}-%{version}-root
> > -Prereq: sh-utils, diffutils, rsync, rcs, mktemp >= 1.5, git-core >= 0.99.3
> > -BuildArchitectures: noarch
> > +BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
> > +Requires: git-core >= 0.99.3
> > +BuildArch: noarch
>
> Why did you remove all the stuff from Requires? They actually are ending
> up adding even trivial stuff like less to it in GIT.
Primary reason is it now requires git, which has those prereqs.
thanks,
-chris
next prev parent reply other threads:[~2005-09-16 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 6:47 [PATCH] Update cogito.spec.in Chris Wright
2005-09-16 11:06 ` Petr Baudis
2005-09-16 15:46 ` Chris Wright [this message]
2005-09-16 18:04 ` Junio C Hamano
2005-09-16 18:09 ` Chris Wright
2005-09-16 19:44 ` Horst von Brand
2005-09-16 20:19 ` Chris Wright
[not found] ` <20050917214807.GA3590@pasky.or.cz>
2005-09-18 17:32 ` [PATCH] cogito: Fix rpm build for 64bit platforms 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=20050916154631.GJ8041@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).