From: Junio C Hamano <gitster@pobox.com>
To: Paul Smith <paul@mad-scientist.net>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Reducing git size by building libgit.so
Date: Thu, 13 Jun 2019 11:23:29 -0700 [thread overview]
Message-ID: <xmqq1rzxwdi6.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <13c40b4b819f702a52f7039177579f87fa90aa50.camel@mad-scientist.net> (Paul Smith's message of "Thu, 13 Jun 2019 13:28:10 -0400")
Paul Smith <paul@mad-scientist.net> writes:
> I assumed that we were discussing providing an _option_ of building
> with shared libraries, rather than removing support for static
> libraries and only supporting shared libraries. The former is the
> typical model in portable projects.
> ...
> So, the answer to most of the (important) issues you and Brian raise
> is, "if it doesn't work, can't be made to work, is too slow, or is
> annoying for ANY other reason, then don't do it".
>
> Regarding things like publish-ability of the API, I don't know what
> else to say. It's FOSS, after all: anyone can do whatever they want
> (with respect to building and using the code) regardless of the desires
> of the development team. All you can do is make clear that the intent
> is that the API is not stable, and if they don't listen and their stuff
> breaks, well, as the saying goes, they get to keep both halves. Not
> adding any header files to the installation rules and packages is also
> helpful :).
>
> There's a certain amount of cold, hard reality that every FOSS project,
> regardless of how friendly and welcoming they aspire to be, simply
> can't avoid while still making progress (and staying sane).
>
>
> I certainly don't want to minimize the amount of work involved here,
> nor do I want to in any way volunteer myself to undertake any of it: as
> I said, I don't have strong feelings about it.
>
> I'm just saying, there's no technical reason it can't be done while
> maintaining the same features (such as relocatability) as the static
> library installs, at least on the major platforms.
>
> Cheers!
next prev parent reply other threads:[~2019-06-13 18:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 19:52 Reducing git size by building libgit.so Elmar Pruesse
2019-06-11 23:48 ` brian m. carlson
2019-06-12 9:29 ` Duy Nguyen
2019-06-12 13:57 ` Paul Smith
2019-06-12 23:31 ` brian m. carlson
2019-06-13 19:19 ` Johannes Sixt
2019-06-13 7:51 ` Johannes Schindelin
2019-06-13 17:28 ` Paul Smith
2019-06-13 18:23 ` Junio C Hamano [this message]
2019-06-12 9:41 ` Ævar Arnfjörð Bjarmason
2019-06-12 9:46 ` Duy Nguyen
2019-06-12 10:25 ` SZEDER Gábor
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq1rzxwdi6.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=paul@mad-scientist.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).