GitLab

This is for fields "extra-source-files", "data-files", "extra-doc-files", "c-sources" and "js-sources"
See https://github.com/haskell/cabal/issues/1531

Also fix some warnings to make it work.

See #2323 for the details.

(cherry picked from commit 370f135a)

path templates.

CompilerInfo contains more information about the compiler than
CompilerId, which just stores the flavour and version. In particular,
CompilerInfo knows an AbiTag, which can be used to tell binary
incompatible results from the same compiler apart, and detailed
information about supported languages and extensions.

Some fields in CompilerInfo may be left unknown (Nothing). This can
be used in the future to allow partially resolving configurations
based on supported languages or extensions.

This patch adds the js-sources field, for JavaScript source code
that should be included in compiled programs, similar to c-sources
for other targets.

It also adds ghcjs-options, ghcjs-shared-options and ghcjs-prof-options
and makes the underlying code for options easier to extend.

There's no chrome here, but some of the guts for Cabal supporting compiling
signatures.  The key UI is a new --instantiate-with flag for ./Setup (no support
cabal-install side!) which properly modifies the package key, calculates extra
hole dependencies for a package, and ensures an appropriately
translated -sig-of is passed to GHC.  The UI here is supremely user-unfriendly:
the intent is that users will use cabal-install to calculate these parameters
for them.

ToDo: Cabal's inconsistency check in ./Setup needs to be adjusted to be
less zealous.
Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Fixes #2195.

Fixes #2130.

Fixes #2162.

Before this, AllrightsReservered had two separate meanings; the author
explicitly chose this license or not license was specified and therefore
defaults to AllRightsReserved.

The default license when no license is specified is now UnspecifiedLicense.

Closes: #2141

Unlike GHC, Cabal will still try to find a globally consistent choice for
all package names, i.e. this does *not* implement private dependencies.
Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

The initial support for module re-exports relied on ghc-pkg to resolve
user-specified re-exports to references to specific installed packages.
This resolution is something that can fail so it's better for Cabal to
do it during the package configure phase.

In addition, it is inconvenient in ghc-pkg to be doing this resolution,
and it just seems fishy as a design. Also, the same ModuleExport type
was being used both for user-specified source re-exports and also for
the specific re-exports in the package db.

This patch splits the type into two: one for source level, and one for
resolved ones for use in the package db. The configure phase resolves
one to the other.

One minor change: it is now possible to re-export a module defined in
the same package that is not itself exported (ie it's in other-modules,
rather than exposed-modules). Previously for modules definied in the
same package they had to be themselves exported. Of course for
re-exports from other packages they have to be exposed.

Pretty print the fields of flags nested.

Re-exported modules allow packages to reexport modules from their
dependencies without having to create stub files.  Reexports of the same
original module don't count as ambiguous imports when module finding
occurs.  The syntax is:

    "orig-pkg" OrigName as NewName

You can omit 'as NewName', in which case it is reexported as the same
name.  Self referential aliases work too; however, they're only visible
to packages which depend on this package.

Left to future work: just provide a module name 'OrigName', where ghc-pkg
figures out what the source package is.
Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Consolidate default values and make flag pretty-printing use them.
Allow code to work with non-boolean defaults.

- Remove redundant space after `description:` field name.
- Eliminate trailing spaces on *some* blank lines.
- Convert all field names to lower case.
- Eliminate redundant `buildable: True` and `exposed: True` fields.
- Fix Haddock module comment.

Added the new field constructor functions 'listFieldWithSep'
and 'commaListFieldWithSep' to be able to define pretty printing
for fields, where each value of the field is positioned on a new line.

Which fields are nested is currently hard coded in the 'ppField' function.

(cherry picked from commit e8d5ea25)

Added the new field constructor functions 'listFieldWithSep'
and 'commaListFieldWithSep' to be able to define pretty printing
for fields, where each value of the field is positioned on a new line.

Which fields are nested is currently hard coded in the 'ppField' function.

This reverts commit fdf8afce.

Fixes #1771.

The list constructors 'nestedListField' and 'nestedCommaListField'
have been added and are now used for fields that should be pretty
printed with nesting.

This reverts commit 0038d05a, reversing
changes made to c721e851.

This reverts commit 68d9077c.

This reverts commit 3c7a7408, reversing
changes made to 68d9077c.

Now the 'fieldGet' function of 'FieldDescr' does the
whole pretty printing of the field. Previously only the
values have been pretty printed by 'fieldGet' and the
name of the field with the colon have been printed
in the 'PrettyPrint' module.

But this separation made it more difficult to handle the
pretty printing of fields differently, because some fields
should be just printed in one lines and others - having several
values - should be printed nested with each value on a new line.

This difference in the printing of the fields is now handled by
the 'FieldDescr' constructor functions in 'ParseUtils'.

Now the 'listField' and 'commaListField' functions create 'FieldDescr'
that nest their values and all other functions create one line
for the whole field.

Fixes #712

It's just noise that duplicates information in the 'LICENSE' file.

Based closely on the patches by Mathieu Boespflug <mboes@cs.mcgill.ca>

This field is intended to be used instead of (or in addition to) the
normal 'license-file' field by packages that have multiple files for
their license material. This is useful when eg the license is
supplemented by additional permissions and/or conditions. Notably,
the LGPL is structured in this way: it amends the GPL with additional
permissions, therefore one should distribute both the GPL in COPYING
and the LGPL in COPYING.LESSER.

So we keep both the license-file and license-files fields (rather than
deprecating one) and packages can use either or a mixture.