Skip to content

AllRightsReserved has two possible meanings #2141

Closed
@erikd

Description

@erikd

Currently a license value of AllRightsReserved has two possible meaining:

  • No license was specified and we are defaulting to AllRightsReserved.
  • The license has been explicitly set to AllRightsReserved because it is, for example, an internal company specific application.

I propose that we allow a distinction to be made between these two to give us:

  • ExplicitAllRightsReserved
  • NoLicenseAllRightsReserved

When reading existing cabal files, "AllRightsReserved" would be converted to ExplicitAllRightsReserved and a missing license field would be interpretted as NoLicenseAllRightsReserved.

Comments?

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