Page MenuHomeFreeBSD

textproc/git-chglog: Update to 0.13.0
ClosedPublic

Authored by lcook on Mar 25 2021, 12:59 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Oct 16, 1:58 AM
Unknown Object (File)
Wed, Oct 15, 10:56 PM
Unknown Object (File)
Sat, Oct 11, 9:44 PM
Unknown Object (File)
Sat, Sep 20, 11:29 PM
Unknown Object (File)
Thu, Sep 18, 1:28 PM
Unknown Object (File)
Aug 3 2025, 11:39 PM
Unknown Object (File)
Aug 2 2025, 8:59 PM
Unknown Object (File)
Jul 25 2025, 5:29 AM
Subscribers

Details

Summary
Test Plan

QA:

  • portlint: OK (looks fine).
  • testport: OK (poudriere: 12.2-RELEASE-p4, amd64/i386).

MFH: No (Feature update only).

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

LGTM.

Just out of curiosity, why do we need BUILDFLAGS now?

This revision is now accepted and ready to land.Mar 25 2021, 4:16 PM

LGTM.

Just out of curiosity, why do we need BUILDFLAGS now?

Versions before this update would hard-code its version string inside the source. So instead, we can pass the appropriate version during the build process via ldflags. See here for the pull-request. It has become a convention nowadays to do this while also making it easier on the maintainer. In some cases, the author of an application forgets to bump the hard-coded value, so this avoids that entirely when packaging up for a system.

This revision was automatically updated to reflect the committed changes.

LGTM.

Just out of curiosity, why do we need BUILDFLAGS now?

Versions before this update would hard-code its version string inside the source. So instead, we can pass the appropriate version during the build process via ldflags. See here for the pull-request. It has become a convention nowadays to do this while also making it easier on the maintainer. In some cases, the author of an application forgets to bump the hard-coded value, so this avoids that entirely when packaging up for a system.

Thanks for the explanation!