More information in the generated modules Paths_<pkgname> and PackageInfo_<pkgname>

[L-TChen]

This PR put more definitions in the automatically generated modules, i.e.

• Paths_<pkgname> includes additionally the path to doc and file names of license files
• PackageInfo_<pkgname> includes many more fields of a package description including bug-reports.
• PackageInfo_<pkgname> is now generated by Zinza.

---

Template Α: This PR modifies cabal behaviour

Include the following checklist in your PR:

• Patches conform to the coding conventions.
• Any changes that could be relevant to users have been recorded in the changelog.
• The documentation has been updated, if necessary.
• Manual QA notes have been included.

Bonus points for added automated tests!

[mpickering]

Is there a ticket which tracks/motivates this change?

[L-TChen]

Is there a ticket which tracks/motivates this change?

It is mostly motivated by #3909 still. As the OP says

By the way: It would be useful to export name and synopsis too, since they often appear in --version or --help.

It appears natural to have the package description avaiable and let authors decide what information should be printed.

For example, it is especially useful to have the field description available, since the description of a package is usually printed if a CLI program expecting some input does not receive any. If this information is scattered here and there, it is likely to have inconsisent descriptions in the package description and in the codebase.

[L-TChen]

The Zinza part is only refactoring: the PackageInfor_<pkgname> is implemented differently from Paths_<pkgname> and it is rather confusing.

[andreabedini]

Please consider cabal-version while working on this. See #9331