You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In trying to figure out how to use license-report for packaging, I've run into
the problem that typically, one wants to write the report to a different path
than where it will end up on the end-user's machine.
In particular, the links to the dependencies' licenses will break if the report
is moved out of licensedir.
Three solutions suggest themselves:
Add another path argument prefix that will be prepended to licensedir when
it comes to writing the dependencies' licenses (i.e. the report will link to
the licenses as if they're saved under licensedir, but they actually will be
saved to prefix/licensedir)
Use relative paths in the report. To avoid desynchronization, perhaps have licensedir imply writing the report to licensedir/$target.md or licensedir/index.md?
In trying to figure out how to use
license-report
for packaging, I've run intothe problem that typically, one wants to write the report to a different path
than where it will end up on the end-user's machine.
In particular, the links to the dependencies' licenses will break if the report
is moved out of
licensedir
.Three solutions suggest themselves:
Add another path argument
prefix
that will be prepended tolicensedir
whenit comes to writing the dependencies' licenses (i.e. the report will link to
the licenses as if they're saved under
licensedir
, but they actually will besaved to
prefix/licensedir
)Use relative paths in the report. To avoid desynchronization, perhaps have
licensedir
imply writing the report tolicensedir/$target.md
orlicensedir/index.md
?Do nothing, and have the end-user fudge the paths. One possible way to do this
(note the
readarray targets
line is due toAdd a cabal target command haskell/cabal#9744)
The text was updated successfully, but these errors were encountered: