From: Johan Herland <johan@herland.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Todd Zullinger <tmz@pobox.com>,
git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: [RFH] rpm packaging failure
Date: Sun, 31 Jan 2010 01:06:52 +0100 [thread overview]
Message-ID: <201001310106.52303.johan@herland.net> (raw)
In-Reply-To: <7vsk9nsemh.fsf@alter.siamese.dyndns.org>
On Saturday 30 January 2010, Junio C Hamano wrote:
> The files that are problematic are only infrastructure bits to support
> "remote helpers written in Python" (which we don't ship at all yet).
>
> Once we start shipping real remote helpers, separating Python bits out
> into its own package would make a lot of sense. People who want to use
> foreign scm helpers that happen to be written in Python would need it,
> and all others don't.
>
> But I suspect that a safer alternative at least for 1.7.0 would be to
> leave these files out altogether. As I understand the current state, it
> is an unused but required package dependency on Python, a downside
> without an upside. Is it Ok with "remote helpers in Python" folks (I
> think Sverre and Johan are principal parties), or did I miss some reason
> that these need to be installed/installable, perhaps to support third
> party packages that already exist?
AFAICS, there's no reason why these should be installed without anything
actually using them. Although I defer to Sverre, who did the last work in
this area.
...Johan
next prev parent reply other threads:[~2010-01-31 0:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 9:24 [RFH] rpm packaging failure Junio C Hamano
2010-01-30 15:19 ` Todd Zullinger
2010-01-30 17:10 ` Junio C Hamano
2010-01-30 19:47 ` Todd Zullinger
2010-01-30 22:22 ` Junio C Hamano
2010-01-31 4:12 ` Todd Zullinger
2010-01-31 19:18 ` Junio C Hamano
2010-01-31 23:14 ` David Aguilar
2010-01-31 23:46 ` David Aguilar
2010-01-31 0:06 ` Johan Herland [this message]
2010-01-31 0:56 ` Sverre Rabbelier
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=201001310106.52303.johan@herland.net \
--to=johan@herland.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=srabbelier@gmail.com \
--cc=tmz@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).