Skip to content

A file that defines a Cabal package should be officially called «Cabal Pact». #8965

@kindaro

Description

@kindaro

problem

It is awkward that there is no officially recognized name for files *.cabal that define a Cabal package. Some other languages call them «manifest». I too was inclined to call them so, for the lack of a better pick. But the word «manifest» is flat, boring, it names a phenomenon that is only short lived.

manifest
3 : a list of passengers or an invoice of cargo for a vehicle (such as a ship or plane)

The Merriam-Webster dictionary.

solution

We have already taken the word «cabal». With a Cabal, one signs a Pact. It also has a fitting connotation of eternal commitment: if you specify version bounds thoroughly, your package will build now and forever, and if you put it to Hackage, you cannot take it back.

With the Haskell Cabal, one Signs a Pact in Blood.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions