git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Fredrik Kuivinen <freku045@student.liu.se>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Why does git-core 0.99.7 require python 2.4?
Date: Mon, 19 Sep 2005 14:00:25 -0700	[thread overview]
Message-ID: <432F26E9.9090707@zytor.com> (raw)
In-Reply-To: <7vslw0lqvd.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:
> Fredrik Kuivinen <freku045@student.liu.se> writes:
> 
>>Not supporting one of the major Linux distributions isn't ideal
>>though, so maybe we should do something about this. I will have a look
>>at rewriting the code to not use subprocess.
> 
> Thanks -- I personally feel that it would be best to just let FC
> catch up, solving this problem for us, while you spend your time
> on other things first.
> 

The problem isn't FC, the problem is RHEL, generally used on machines 
for which an OS update it's huge deal.

> Peter, if you feel strongly about it I'd do 0.99.7.1 removing
> the 'requires python >=2.4', but as Fredrik says the only thing
> that uses Python 2.4 is his recursive merge, and it is not
> something we use without the user explicitly asking for it.  We
> can consider it as the same status as send-email or archimport
> which cannot work without Perl modules necessary for their
> operation, so if you can install bypassing requires- check that
> would work equally well.

My suggestion would be to fork off the recursive merge into a separate 
binary package which can have the python >= 2.4 requirement (unless 
Fredrik just fixes it.)

	-hpa

  reply	other threads:[~2005-09-19 21:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-19 19:07 Why does git-core 0.99.7 require python 2.4? H. Peter Anvin
2005-09-19 20:02 ` Fredrik Kuivinen
2005-09-19 20:55   ` Junio C Hamano
2005-09-19 21:00     ` H. Peter Anvin [this message]
2005-09-19 21:22       ` Junio C Hamano
2005-09-19 21:33         ` H. Peter Anvin
2005-09-19 21:49         ` H. Peter Anvin
2005-09-19 23:17           ` jepler
2005-09-19 23:24             ` H. Peter Anvin
2005-09-20  2:02               ` Junio C Hamano
2005-09-20  4:39                 ` Ship our own copy of subprocess.py Junio C Hamano
2005-09-20  4:41                   ` H. Peter Anvin
2005-09-20  5:30                   ` Fredrik Kuivinen
2005-09-20 14:55                     ` Linus Torvalds
2005-09-20 17:58                       ` H. Peter Anvin
2005-09-20  6:14                   ` Chris Wright
2005-09-20  6:36                     ` Junio C Hamano
2005-09-20 17:56                       ` 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=432F26E9.9090707@zytor.com \
    --to=hpa@zytor.com \
    --cc=freku045@student.liu.se \
    --cc=git@vger.kernel.org \
    --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).