Skip to content

Conversation

@geekosaur
Copy link
Collaborator

@geekosaur geekosaur commented Dec 11, 2025

I'm not sure if this counts as a significant change or not, since it's possible scripts depend on the output. (The git info change doesn't really count, since it's only operable on unreleased versions.)

hilfy «cabal+more-version-info¤@a11e10471» Z$ $(cabal list-bin cabal) --version
Warning: this is a debug build of cabal-install with assertions enabled.
cabal-install version 3.17.0.0 (commit a11e104 on more-version-info, Thu Dec 11 16:57:14 2025 +0000)
compiled using version 3.17.0.0 of the Cabal library (commit de16351, Thu Nov 27 00:06:37 2025 +0000)
with ghc 9.10.3 on linux x86_64

The information added by this change is the last line. If a development GHC version is used to build cabal, the version will include a datestamp (e.g. 9.14.0.20251128).

Template Α: This PR modifies behaviour or interface

Include the following checklist in your PR:

@geekosaur
Copy link
Collaborator Author

This is a proposed change, and open to review and suggestions.

Copy link
Member

@Mikolaj Mikolaj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ulysses4ever
Copy link
Collaborator

ulysses4ever commented Dec 12, 2025

Can you show how it'll look like in the description? Also, it'd be good to add some motivation. Remember that by default we expect a ticket before a PR.

@geekosaur
Copy link
Collaborator Author

The motivation was trying to get that information from someone on Discord who was having odd problems with cabal, and IIRC it turned out they were using a cross-built cabal.

I don't consider this final by any means; some programs have a --version-full option, for example, which includes this kind of information (and the GIT_REV stuff might also move there if we add it).

@geekosaur geekosaur force-pushed the more-version-info branch 2 times, most recently from 916c671 to aa47f49 Compare December 12, 2025 23:02
@geekosaur
Copy link
Collaborator Author

I moved that #if to a new Distribution.Client.Compat.SysInfo module.

I'm not sure if this counts as a significant change or not, since
it's possible scripts depend on the output. (The git info change
doesn't really count, since it's only operable on unreleased
versions.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants