<feed xmlns='http://www.w3.org/2005/Atom'>
<title>jcarr/libgit2/script, branch devel</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>http://cgit.wit.com/jcarr/libgit2/atom?h=devel</id>
<link rel='self' href='http://cgit.wit.com/jcarr/libgit2/atom?h=devel'/>
<link rel='alternate' type='text/html' href='http://cgit.wit.com/jcarr/libgit2/'/>
<updated>2024-12-17T21:01:59Z</updated>
<entry>
<title>rename as libgit2</title>
<updated>2024-12-17T21:01:59Z</updated>
<author>
<name>Jeff Carr</name>
<email>jcarr@wit.com</email>
</author>
<published>2024-12-17T21:01:59Z</published>
<link rel='alternate' type='text/html' href='http://cgit.wit.com/jcarr/libgit2/commit/?id=585a8dbbe57e3538ad2acaef58c3bf8bb238e000'/>
<id>urn:sha1:585a8dbbe57e3538ad2acaef58c3bf8bb238e000</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Allow building libgit2 with Chromium zlib (#831)</title>
<updated>2021-09-06T12:13:55Z</updated>
<author>
<name>lhchavez</name>
<email>lhchavez@lhchavez.com</email>
</author>
<published>2021-09-06T12:13:55Z</published>
<link rel='alternate' type='text/html' href='http://cgit.wit.com/jcarr/libgit2/commit/?id=c6da3b97a8a2c7bbbed4496f50c990a1aab4f7bf'/>
<id>urn:sha1:c6da3b97a8a2c7bbbed4496f50c990a1aab4f7bf</id>
<content type='text'>
This change allows the caller to set the `USE_CHROMIUM_ZLIB=ON`
environment variable to use the Chromium implementation of zlib when
building libgit2.</content>
</entry>
<entry>
<title>Add support for managed SSH transport #minor (#814)</title>
<updated>2021-09-06T00:04:40Z</updated>
<author>
<name>lhchavez</name>
<email>lhchavez@lhchavez.com</email>
</author>
<published>2021-09-06T00:04:40Z</published>
<link rel='alternate' type='text/html' href='http://cgit.wit.com/jcarr/libgit2/commit/?id=70e5e419cf0cab31553b106267a0296f3cd672d9'/>
<id>urn:sha1:70e5e419cf0cab31553b106267a0296f3cd672d9</id>
<content type='text'>
This change drops the (hard) dependency on libssh2 and instead uses Go's
implementation of SSH when libgit2 is not built with it.</content>
</entry>
<entry>
<title>Add support for managed HTTP/S transports (#810)</title>
<updated>2021-09-05T23:39:07Z</updated>
<author>
<name>lhchavez</name>
<email>lhchavez@lhchavez.com</email>
</author>
<published>2021-09-05T23:39:07Z</published>
<link rel='alternate' type='text/html' href='http://cgit.wit.com/jcarr/libgit2/commit/?id=b983e1daebf528443e2a3954cd595fa3664ec93f'/>
<id>urn:sha1:b983e1daebf528443e2a3954cd595fa3664ec93f</id>
<content type='text'>
This change uses the newly-exposed Transport interface to use Go's
implementation of http.Client instead of httpclient via libgit2.</content>
</entry>
<entry>
<title>Declare forward-compatibility with libgit2 v1.2.0  #minor (#800)</title>
<updated>2021-09-05T03:07:24Z</updated>
<author>
<name>lhchavez</name>
<email>lhchavez@lhchavez.com</email>
</author>
<published>2021-09-05T03:07:24Z</published>
<link rel='alternate' type='text/html' href='http://cgit.wit.com/jcarr/libgit2/commit/?id=549706bb573653469fbcc35c839759987c318d0c'/>
<id>urn:sha1:549706bb573653469fbcc35c839759987c318d0c</id>
<content type='text'>
We can't yet ship a fully libgit2 v1.2.0-compatible library due to a
missing public symbol, but we can allow the v1.1.0-era codebase to link
against libgit2 v1.2.0 in the meantime.</content>
</entry>
<entry>
<title>Add `NewCredentialSSHKeyFromSigner` (#706)</title>
<updated>2020-12-06T19:55:04Z</updated>
<author>
<name>lhchavez</name>
<email>lhchavez@lhchavez.com</email>
</author>
<published>2020-12-06T19:55:04Z</published>
<link rel='alternate' type='text/html' href='http://cgit.wit.com/jcarr/libgit2/commit/?id=abf02bc7d79dfb7b0bbcd404ebecb202cff2a18e'/>
<id>urn:sha1:abf02bc7d79dfb7b0bbcd404ebecb202cff2a18e</id>
<content type='text'>
This change adds `NewCredentialSSHKeyFromSigner`, which allows idiomatic
use of SSH keys from Go. This also lets us spin off an SSH server in the
tests.</content>
</entry>
<entry>
<title>Build improvements (#707)</title>
<updated>2020-12-06T14:13:38Z</updated>
<author>
<name>lhchavez</name>
<email>lhchavez@lhchavez.com</email>
</author>
<published>2020-12-06T14:13:38Z</published>
<link rel='alternate' type='text/html' href='http://cgit.wit.com/jcarr/libgit2/commit/?id=54afccfa0f5a5574525cbba3b4568cbda252a3df'/>
<id>urn:sha1:54afccfa0f5a5574525cbba3b4568cbda252a3df</id>
<content type='text'>
This change makes the test be verbose and use parallelization if
possible (when using gmake to build).</content>
</entry>
<entry>
<title>Mark some symbols to be deprecated #minor (#698)</title>
<updated>2020-12-05T15:23:44Z</updated>
<author>
<name>lhchavez</name>
<email>lhchavez@lhchavez.com</email>
</author>
<published>2020-12-05T15:23:44Z</published>
<link rel='alternate' type='text/html' href='http://cgit.wit.com/jcarr/libgit2/commit/?id=137c05e802d5e11a5ab54809bc8be8f61ccece21'/>
<id>urn:sha1:137c05e802d5e11a5ab54809bc8be8f61ccece21</id>
<content type='text'>
This change introduces the file deprecated.go, which contains any
constants, functions, and types that are slated to be deprecated in the
next major release.

These symbols are deprecated because they refer to old spellings in
pre-1.0 libgit2. This also makes the build be done with the
`-DDEPRECATE_HARD` flag to avoid regressions.

This, together with
[gorelease](https://godoc.org/golang.org/x/exp/cmd/gorelease)[1] should
make releases safer going forward.

1: More information about how that works at
   https://go.googlesource.com/exp/+/refs/heads/master/apidiff/README.md</content>
</entry>
<entry>
<title>Relax libgit2 minor version check (#696)</title>
<updated>2020-11-28T19:10:34Z</updated>
<author>
<name>nmeum</name>
<email>soeren+github@soeren-tempel.net</email>
</author>
<published>2020-11-28T19:10:34Z</published>
<link rel='alternate' type='text/html' href='http://cgit.wit.com/jcarr/libgit2/commit/?id=1fabe95fb7275df980ff6ab03fb85eac91c5849d'/>
<id>urn:sha1:1fabe95fb7275df980ff6ab03fb85eac91c5849d</id>
<content type='text'>
The major version must still be an exact match since libgit2 uses
semantic versioning and changes to the major number indicate backwards
incompatible changes to the API.

Fixes: #695</content>
</entry>
<entry>
<title>feat: Enable change the system install path (#653)</title>
<updated>2020-10-01T00:27:48Z</updated>
<author>
<name>Suhaib Mujahid</name>
<email>suhaibmujahid@gmail.com</email>
</author>
<published>2020-10-01T00:27:48Z</published>
<link rel='alternate' type='text/html' href='http://cgit.wit.com/jcarr/libgit2/commit/?id=111185838cebe3415e47c75e67fb81295952ce68'/>
<id>urn:sha1:111185838cebe3415e47c75e67fb81295952ce68</id>
<content type='text'>
#### Problem:
The current `CMAKE_INSTALL_PREFIX` value for the `system` build mode is `/usr`. However, in`macOS` as an example, you cannot write to `/usr` without `sudo` permission.

#### Proposed solution:
Enable changing the value to `/usr/local` (or any other path). This change makes the script use the value of the environment variable `SYSTEM_INSTALL_PREFIX` to select the installation path.  If the variable is not set, it fallback to the path `/usr`.</content>
</entry>
</feed>
