public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "mlists@x76.eu" <mlists@x76.eu>
To: cygwin@cygwin.com
Subject: Re: Git without SSH Server and cygrunsrv
Date: Wed, 14 Jun 2017 05:39:00 -0000	[thread overview]
Message-ID: <312b3b9b-a2f5-424f-53af-4ff347158560@x76.eu> (raw)
In-Reply-To: <20170613102245.GH25777@dinwoodie.org>

Thank you for the explanation Adam.

Last question: How much more is the workload for maintaining a "splitted
package"?

I understand I can contribute with patches but if it would increase the
workload for the maintainers, then I think there's no point in doing it.

Regards


On 2017-06-13 17:22, Adam Dinwoodie wrote:
> On Tue, Jun 13, 2017 at 05:59:45AM +0200, Marco Atzeri wrote:
>> On 13/06/2017 02:13, mlists wrote:
>>> Hi,
>>> how can I install Git without binutils, cygrunsrv, python and OpenSSH
>>> server?
>>>
>>> I want to work with remote repositories using clone/pull/push, built
>>> would like to avoid having to install a ton of other things that won't
>>> be used.
>> cygrunsrv is part of the cygwin package.
> This isn't true: cygrunserv is pulled in as an openssh dependency.
>
>> python is a dependency of git
>>  (due to /usr/libexec/git-core/git-p4)
> I have a vague intention of separating out git-p4 into a separate
> package, primarily so that the core git package doesn't need to require
> python.  However, I haven't got to that work for some time, and it's not
> likely to make it up my priority list any time soon either.  If you know
> you're not going to use git-p4, you can manually skip the python
> dependency selection.
>
> If you want to avoid having to deselect the python package using the
> (admittedly awkward) setup-*.exe interface, I'd gratefully take patches
> and pull requests for this work, either on this list or on the GitHub
> repository: <https://github.com/me-and/Cygwin-Git>.
>
>> you don't need the openssh server but you need the client
>> and they are in the same package.
> Likewise, if you know you're not going to need the SSH client (which
> will depend on how you're interacting with the remote repositories), you
> can deselect it at installation time.
>
> Given (a) openssh is a small package even including all its dependencies
> (totals about 750 kiB by my count) and (b) connecting via SSH is a
> mainline use case for Git, I'm not going to change the Cygwin git
> packages to skip this dependency.  If you really want Git without SSH
> support, you'll need to compile it from source yourself.
>
> You could try petitioning the OpenSSH maintainer, Corinna, to split the
> package into openssh-client and openssh-server or similar, which would
> reduce some of the dependencies, but for similar reasons I can't imagine
> there's much appitite for that.
>
>> If you are programming you need binutils anyway.
> Likely true.  In any case, binutils is currently being pulled in via the
> python package and git-p4, so as soon as I / someone does the work to
> split git-p4 out into a separate package, binutils will stop being a
> dependency of the core git package.
>
> Adam
> (Your local friendly Cygwin Git maintainer)
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2017-06-14  5:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13  0:13 mlists
2017-06-13  4:00 ` Marco Atzeri
2017-06-13 10:22   ` Adam Dinwoodie
2017-06-14  5:39     ` mlists [this message]
2017-07-03 12:25       ` Adam Dinwoodie
2017-06-15 16:41     ` [PATCH git] Separate git-p4 subpackage Yaakov Selkowitz
2017-07-03 12:21       ` Adam Dinwoodie

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=312b3b9b-a2f5-424f-53af-4ff347158560@x76.eu \
    --to=mlists@x76.eu \
    --cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).