Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Take format specification history back to Cabal-1.0 #10847

Merged
merged 1 commit into from
Apr 8, 2025
Merged

Conversation

mpilgrem
Copy link
Collaborator

@mpilgrem mpilgrem commented Mar 23, 2025

The motivation is that the documentation of the history of the format specification is almost complete (it currently stops at Cabal 1.8). This will complete it.

Some background to early Cabal version numbering is available here.

The format specification appears to have been stable between Cabal 1.2.1 and Cabal 1.6.

This PR does not modify behaviour or interface

  • Patches conform to the coding conventions.
    Not applicable, but aims to be consistent with existing text.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).
    Not applicable.

@mpilgrem mpilgrem marked this pull request as draft March 23, 2025 22:40
@mpilgrem mpilgrem force-pushed the to-spec-origin branch 6 times, most recently from 1cec7c8 to d8af336 Compare March 26, 2025 20:50
@mpilgrem mpilgrem marked this pull request as ready for review March 26, 2025 21:05
@mpilgrem mpilgrem requested review from Mikolaj and geekosaur March 26, 2025 21:06
@mpilgrem mpilgrem force-pushed the to-spec-origin branch 2 times, most recently from e8a0e71 to cbb696c Compare March 29, 2025 18:19
@philderbeast
Copy link
Collaborator

@mpilgrem on the cabal website there are some versions of the cabal specification too. Not available at https://www.haskell.org/cabal/, but included with its repository https://github.com/haskell/cabal-website.

With haskell/cabal-website#43, that can be previewed at https://cabal.blockscope.com/pages/history.html, those cabal specifications can be viewed under the history menu.

@mpilgrem mpilgrem force-pushed the to-spec-origin branch 2 times, most recently from d7d05fb to 8ab3b04 Compare March 31, 2025 20:55
@mpilgrem
Copy link
Collaborator Author

mpilgrem commented Mar 31, 2025

@philderbeast Thanks! For the purpose of the modern Cabal User Guide, I decided to treat everything before the Cabal-1.0 provided with GHC 6.4 as 'pre-history'. However, your website did help me track down:

which must be close to the 'source of the Nile'.

Copy link
Member

@andreasabel andreasabel left a comment

Choose a reason for hiding this comment

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

Interesting read!
(I am in no position to verify this information, but I trust you did your homework.)

@mpilgrem mpilgrem added the merge me Tell Mergify Bot to merge label Apr 5, 2025
@mergify mergify bot added ready and waiting Mergify is waiting out the cooldown period merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days labels Apr 5, 2025
@mergify mergify bot merged commit 2f3a45d into master Apr 8, 2025
54 checks passed
@mergify mergify bot deleted the to-spec-origin branch April 8, 2025 00:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days merge me Tell Mergify Bot to merge ready and waiting Mergify is waiting out the cooldown period
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants