Date: Fri, 15 Jun 2018 09:57:52 +0200 From: Michael Gmelin <freebsd@grem.de> To: Adam Weinberger <adamw@adamw.org> Cc: mqudsi@neosmart.net, freebsd-ports@freebsd.org Subject: Re: Removing git dependencies on perl5 and python27 Message-ID: <0DF706C2-DD9D-45DB-968F-8599D88D7622@grem.de> In-Reply-To: <CAP7rwciw%2BhzTcH1qrdTix1HJKci9-PVmzXfyeVk6OYbg7DgGDg@mail.gmail.com> References: <CACcTrKebiP4BCK6F6FaCV8wJggstcSxmSGv9d=iFzYdtaLn-sw@mail.gmail.com> <CAP7rwciw%2BhzTcH1qrdTix1HJKci9-PVmzXfyeVk6OYbg7DgGDg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 15. Jun 2018, at 05:57, Adam Weinberger <adamw@adamw.org> wrote: >=20 >> On Thu, Jun 14, 2018 at 8:16 PM Mahmoud Al-Qudsi <mqudsi@neosmart.net> wr= ote: >>=20 >> Hello list, >>=20 >> I'm probably not alone in considering git to be a core development tool, >> perhaps just a notch or two below the C compiler. `git` and `sudo` are th= e two >> packages I first install (after `pkg` itself) on any machine, and in many= >> cases that suffices to get a basic development environment going. >>=20 >> However, the git package currently brings in a host of unwanted dependenc= ies, >> and I *believe* they can be done without. >>=20 >> This is the complete dependency graph for the git package [0] (generated w= ith >> the newly-minted pkg-graph [1]). It pulls in perl5 and python27, both siz= eable >> packages and both not required to use git. >>=20 >> While git can be compiled without some of the additional dependencies suc= h as >> expat or pcre, this results in a "crippled" git lacking in some core feat= ures, >> and requires special build-time definitions like NO_EXPAT or NO_PCRE pass= ed to >> the git Makefile. The other dependencies like curl, pcre, and gettext are= also >> relatively small and typically part of even the most minimal system, but p= erl5 >> and python27 are full-blown runtimes for interpreted languages that have >> fallen out of favor and have been successfully stripped from FreeBSD core= (and >> even many Linux distributions). >>=20 >> I'm sure these packages are not just there to have a good time and they s= erve >> some purpose and enable a subset of the git functionality, but my questio= n >> here today is whether that functionality is worth its weight in dependenc= ies, >> and whether the ports team is open to seeing the git package stripped of t= hese >> dependencies. >>=20 >> (Obviously the option of adding a "git-lite" package =C3=A0 la "vim-lite"= also >> exists, but I think it's fair to say that would be an ugly and unnecessar= y >> compromise.) >>=20 >> [0]: https://goo.gl/hozu1b >> [1]: https://github.com/neosmart/pkg-graph >=20 > Agreed. I'd personally much rather see small default packages and > -kitchensink slaves, than massive default packages and -lite slaves. > It's always struck me as odd that our git package comes with CVS and > Perforce support. >=20 > # Adam >=20 >=20 Last time I checked, building git without Perl broke submodules (which is a c= ore feature that should work with a default installation). Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0DF706C2-DD9D-45DB-968F-8599D88D7622>