Changes between Initial Version and Version 1 of Ticket #67293, comment 1


Ignore:
Timestamp:
Apr 23, 2023, 1:10:33 AM (13 months ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #67293, comment 1

    initial v1  
    1 It is never a program's choice by what name to link with a library; it is always the library's choice. And libgit2 has evidently chosen to embed a three-digit major version number in the library name. Anytime the library name changes, including due to a major version increase, every port that links with the library must be revbumped. Looks like [https://github.com/macports/macports-ports/pull/18310 the PR that updated libgit2] revbumped some ports that link with libgit2 but not cargo-c.
     1It is never a program's choice by what name to link with a library; it is always the library's choice. And libgit2 has evidently chosen to embed a three-part major version number in the library name. Anytime the library name changes, including due to a major version increase, every port that links with the library must be revbumped. Looks like [https://github.com/macports/macports-ports/pull/18310 the PR that updated libgit2] revbumped some ports that link with libgit2 but not cargo-c.
    22
    33There is [https://github.com/macports/macports-ports/pull/18345 another PR to update cargo-c]; that would take care of this issue for cargo-c.