digital-asset
Ability to exclude dependency packages from DAR
What is the problem you want to solve?
Currently, dependencies and data-dependencies will include the corresponding packages when building a dar.
As a result, the dar becomes self-sustaining, which is desirable in most cases.
However, there are scenarios in which including dependency packages introduces an unnecessary overhead. For example, when building an upgrade project, the dependencies already reside on the ledger.
What is the solution you would propose?
Perhaps parse a new section excluded-dependencies within daml.yaml.
Describe alternatives you've considered
Splitting the codebase further into multiple DARs is not always straightforward, or at the very least, can be cumbersome.
Additional context
Uploading a dar to the ledger can quickly result in a grpc message exceeds maximum size, a setting that is not always easily adjustable.
Currently under discussion here: https://docs.google.com/document/d/16nfIFOh4DTlwZ7VrnLznj4on4CuqIQBOYFjfl_aILJs/edit#heading=h.j1o9vy5fqmrz
