[PATCH] remove Obsoletes from cogito.spec.in

[PATCH] remove Obsoletes from cogito.spec.in

[Chris Wright]

This is leftover from early naming, and is no longer relevant.

Signed-off-by: Chris Wright <chrisw@osdl.org>
---

diff --git a/cogito.spec.in b/cogito.spec.in
--- a/cogito.spec.in
+++ b/cogito.spec.in
@@ -7,7 +7,6 @@ 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
-Obsoletes:	git
 BuildRequires:	zlib-devel, openssl-devel, curl-devel
 BuildRoot:	%{_tmppath}/%{name}-%{version}-root
 Prereq: 	sh-utils, diffutils, rsync, rcs, mktemp >= 1.5

Re: [PATCH] remove Obsoletes from cogito.spec.in

[Petr Baudis]

Dear diary, on Tue, Jul 12, 2005 at 02:33:45AM CEST, I got a letter
where Chris Wright <chrisw@osdl.org> told me that...
> This is leftover from early naming, and is no longer relevant.
> 
> Signed-off-by: Chris Wright <chrisw@osdl.org>

Thanks, applied. BTW, Josh Boyer of Fedora suggested having the

	Provides: git

line in cogito.spec.in as long as it comes with git bundled (which will
be so until git stabilizes, doesn't break backwards compatibility once
in a while, and gets into some regular and reasonably frequent release
cycle). What do you think?

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
<Espy> be careful, some twit might quote you out of context..

Re: [PATCH] remove Obsoletes from cogito.spec.in

[Chris Wright]

* Petr Baudis (pasky@suse.cz) wrote:
> where Chris Wright <chrisw@osdl.org> told me that...
> > This is leftover from early naming, and is no longer relevant.
> > 
> > Signed-off-by: Chris Wright <chrisw@osdl.org>
> 
> Thanks, applied. BTW, Josh Boyer of Fedora suggested having the
> 
> 	Provides: git
> 
> line in cogito.spec.in as long as it comes with git bundled (which will
> be so until git stabilizes, doesn't break backwards compatibility once
> in a while, and gets into some regular and reasonably frequent release
> cycle). What do you think?

Hmm, in an ideal world all of those stipulations are right around the
corner.  Also, if the split is done, then cogito can depend on a specific
version of git-core, to help isolate against those upstream changes.
The main thing then is getting any local changes you have pushed to
Linus' git tree (if there are still any).

Adding Provides is probably only useful if there's some other package
that's relying on git being there (i.e. gitweb perhaps).  I guess we
can add that, and remove it when there's proper dependencies in order.
May as well do git-core as is now done in git.

thanks,
-chris
--



Mark cogito rpm package as providing git-core, since it currently does.

Signed-off-by: Chris Wright <chrisw@osdl.org>
---

diff --git a/cogito.spec.in b/cogito.spec.in
--- a/cogito.spec.in
+++ b/cogito.spec.in
@@ -10,6 +10,7 @@ Source: 	http://kernel.org/pub/software/
 BuildRequires:	zlib-devel, openssl-devel, curl-devel
 BuildRoot:	%{_tmppath}/%{name}-%{version}-root
 Prereq: 	sh-utils, diffutils, rsync, rcs, mktemp >= 1.5
+Provides:	git-core
 
 %description
 GIT comes in two layers. The bottom layer is merely an extremely fast