Cabal custom setup

[snoyberg]

Note: Documentation fixes for https://docs.haskellstack.org/en/stable/ should target the "stable" branch, not master.

Please include the following checklist in your PR:

• Any changes that could be relevant to users have been recorded in the ChangeLog.md
• The documentation has been updated, if necessary.

I'm still testing this in a more complex use case. However, the simple test case I devised was:

• stack new foo

• Modify the Setup.hs file to add import Acme.Missiles

• Add acme-missiles-0.3 as an extra-dep

• Add the following custom-setup block to foo.cabal:

  custom-setup
    setup-depends: base >= 4.6,
                   Cabal >= 1.24 && < 1.25,
                   acme-missiles
  

• Set build-type to Custom

• Confirm that without the patch, the package refuses to compile. With the patch, it compiles just fine.

@borsboom Maybe we can sync up later on adding this as an integration test case?

[decentral1se]

s/setings/settings/g

[decentral1se]

s/configuraiton/configuration/g

[metaleap]

Just what I need! This isn't out yet right? I have stack v1.3.2 and get:

Cabal file warning in path/testdep.cabal: Ignoring unknown section type: custom-setup

Curious, will this be in 1.3.3?

Edit: I see from the commit it's for 1.4, cool

[decentral1se]

@metaleap, try stack upgrade --git and stack setup --ugrade-cabal.

The functionality is in HEAD.

[metaleap]

I would, had I not just found out about stack's explicit-setup-deps which let's me proceed with business luckily =) (btw probly cu at one of the upcoming Berlin Haskell meetups as soon as the snow&ice melt away!)

[decentral1se]

btw probly cu at one of the upcoming Berlin Haskell meetups

Ah! It would be cool but I already moved city. But send my regards! Good people. 👍