From: "James Bowes" <jbowes@dangerouslyinc.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Make the git metapackage require the same version of the subpackages.
Date: Sun, 6 Jan 2008 16:13:26 -0500 [thread overview]
Message-ID: <3f80363f0801061313o514fa01bje354503483db47ab@mail.gmail.com> (raw)
In-Reply-To: <7vprwe4s8e.fsf@gitster.siamese.dyndns.org>
On Jan 6, 2008 3:24 PM, Junio C Hamano <gitster@pobox.com> wrote:
> James Bowes <jbowes@dangerouslyinc.com> writes:
>
> > Without explicit version deps in the rpm spec file, 'yum update git'
> > effectively does nothing. Require explicit versions of the subpackages, so that
> > they get pulled in on an update.
> >
> > Signed-off-by: James Bowes <jbowes@dangerouslyinc.com>
>
> I am asking as an RPM illiterate, not questioning the validity
> of what your patch does.
>
> The approach your patch takes feels like the right way we should
> have taken from the beginning. Does this supersede the "fix" in
> 5587cac28be66acf5edc2a4b83b67c8cfffbc5e9 (GIT 1.5.3.1: obsolete
> git-p4 in RPM spec file)? IOW, if we had Requires for the same
> version from the beginning, we wouldn't have had the problem
> when we dropped git-p4 package?
I believe the obsolete is still needed, as you'd need a way to tell
rpm to just get rid of git-p4 entirely.
-James
next prev parent reply other threads:[~2008-01-06 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-06 17:35 [PATCH] Make the git metapackage require the same version of the subpackages James Bowes
2008-01-06 20:24 ` Junio C Hamano
2008-01-06 21:13 ` James Bowes [this message]
2008-01-06 21:24 ` Junio C Hamano
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=3f80363f0801061313o514fa01bje354503483db47ab@mail.gmail.com \
--to=jbowes@dangerouslyinc.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).