add paragraph mentioning stackage #11018
Conversation
L0neGamer
force-pushed
the
import-stackage-doc
branch
from
5a87bc7 to
3466e90
Compare
| ``import: https://www.stackage.org/lts-21.25/cabal.config`` in your | ||
| ``cabal.project``. Note that Stackage does not guarantee that these will work | ||
| with regards to revisions. | ||
|
|
There was a problem hiding this comment.
This will not work if there are any version constraint conflicts.
Not being able to override versions and not being able to specify revisions are shortcomings of cabal.
If we are going to suggest doing this, can we also say how to mitigate the version constraint conflicts. The simple fix is to download the stackage-hosted cabal.config and remove (comment out) the conflicting contraints. I describe how to do this in the Stackage Resolver and Constraints section of the Updo readme.
On https://github.com/up-do, I've converted projects to use Updo and use a Stackage resolver. Most of these have a ./project-stackage folder (that's where I put the downloaded cabal.config files) and had version constraint conflicts.
There was a problem hiding this comment.
Adding more caveats sounds like a good idea - too.
| @@ -85,6 +85,13 @@ architecture and version information from, which will force some | |||
| commands (update, sdist) to require ghc present where otherwise it | |||
| would not be necessitated. | |||
|
|
|||
| One use case for imports is to specify a `Stackage <https://www.stackage.org/>` | |||
| snapshot, so that your cabal project can use the same set of packages as | |||
| that snapshot. To use the ``lts-21.25`` resolver, you can write | |||
There was a problem hiding this comment.
Could you link to the cookbook reproducible builds section that already mentions importing from stackage?
There was a problem hiding this comment.
Great idea, I'll get on that when I can.
There was a problem hiding this comment.
@Kleidukos sorry to ping you about this, do you know of a way to link to a different RST document without making it full link?
| To mitigate these shortcomings, you can download the config file that is linked | ||
| to and remove the troublesome constraints. |
There was a problem hiding this comment.
| To mitigate these shortcomings, you can download the config file that is linked | |
| to and remove the troublesome constraints. | |
| To mitigate these shortcomings, download the linked ``cabal.config`` file, import this locally with a relative path and repeatedly ``cabal build all --dry-run`` to identify and then comment out version constraint conflicts until the cabal solver is happy. |
Minor documentation addition to express a specific usecase for config importing, that of using stackage as your package set.
@Kleidukos as requested.