* Petr Baudis ([EMAIL PROTECTED]) wrote:
> where Chris Wright <[EMAIL PROTECTED]> told me that...
> > This is leftover from early naming, and is no longer relevant.
> > Signed-off-by: Chris Wright <[EMAIL PROTECTED]>
> 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.
Mark cogito rpm package as providing git-core, since it currently does.
Signed-off-by: Chris Wright <[EMAIL PROTECTED]>
diff --git 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
Prereq: sh-utils, diffutils, rsync, rcs, mktemp >= 1.5
GIT comes in two layers. The bottom layer is merely an extremely fast
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html