Updated yesod-bin
66 views
Skip to first unread message
Michael Snoyman
Aug 20, 2015, 1:52:37 AM8/20/15
to yeso...@googlegroups.com
Anton Gushcha reported a bug when using `yesod devel` which prevented changes to the site from appearing. Blake Rain diagnosed this to a problem with package database order. I've just released a new version of yesod-bin (1.4.14) which should resolve the issue. This bug would have affected both stack and cabal sandbox users[1]. I'd recommend upgrading.
stack users: you can modify your stack.yaml file to include:```
```
[1] Reason being: anyone with multiple package databases would have been affected.
Michael Snoyman
Aug 23, 2015, 4:11:00 AM8/23/15
to Aaron Wolf, Yesod Web Framework
I'm sure stack best practices will evolve over time, but AFAICT there's no downside to include yesod-bin in the extra-deps.
And yes, yesod-bin still relies on cabal-install, though the upcoming wai-devel will not.On Sun, Aug 23, 2015 at 12:23 AM, Aaron Wolf <wolf...@gmail.com> wrote:
Some minor questions:
Is it good form to include yesod-bin in stack.yaml even though a yesod site doesn't *actually* depend on yesod-bin (because the site itself can work otherwise, yesod-bin is just used for development such as `yesod devel`) ? As I think about it, I suppose including yesod-bin in stack.yaml but *not* in the .cabal file makes some sense. But the alternative is to tell developers to manually `stack build yesod-bin-1.4.14` and leave it out of the formal stack.yaml. Mostly just looking for guidance on best practice here. Seems almost like putting yesod-bin in the stack.yaml is like including hlint in the stack.yaml (or the .cabal) even though it's just a development tool and not a real dependency…
Next, is a manual install of cabal-install still needed as per the original announcement of yesod-bin stack compatibility or does yesod-bin now include cabal-install as its own dependency? (obviously, I hope yesod devel will soon be updated to just use the already built stuff from stack and basically call stack and not have to interact with cabal-install at all).
Michael Snoyman
Aug 23, 2015, 1:05:02 PM8/23/15
to Aaron Wolf, Yesod Web Framework
No, I'm not tweaking those usage instructions at all. I'm just recommending that people upgrade yesod-bin.
On Sun, Aug 23, 2015, 8:01 PM Aaron Wolf <wolf...@gmail.com> wrote:
I suspected yesod-bin still requires cabal-install, but the initial yesod-bin for stack blog post mentioned manually using stack to build cabal-install. So, does it now work to only make yesod-bin explicit and it will itself know to include cabal-install as a dependency, not needing to do anything explicit to get cabal-install?
Aaron Wolf
Aug 23, 2015, 1:05:46 PM8/23/15
to Michael Snoyman, Yesod Web Framework
I suspected yesod-bin still requires cabal-install, but the initial yesod-bin for stack blog post mentioned manually using stack to build cabal-install. So, does it now work to only make yesod-bin explicit and it will itself know to include cabal-install as a dependency, not needing to do anything explicit to get cabal-install?
On Sun, Aug 23, 2015 at 1:10 AM, Michael Snoyman <mic...@snoyman.com> wrote:
Aaron Wolf
Aug 23, 2015, 1:05:46 PM8/23/15
to Yesod Web Framework, mic...@snoyman.com
Some minor questions:
Is it good form to include yesod-bin in stack.yaml even though a yesod site doesn't *actually* depend on yesod-bin (because the site itself can work otherwise, yesod-bin is just used for development such as `yesod devel`) ? As I think about it, I suppose including yesod-bin in stack.yaml but *not* in the .cabal file makes some sense. But the alternative is to tell developers to manually `stack build yesod-bin-1.4.14` and leave it out of the formal stack.yaml. Mostly just looking for guidance on best practice here. Seems almost like putting yesod-bin in the stack.yaml is like including hlint in the stack.yaml (or the .cabal) even though it's just a development tool and not a real dependency…
Next, is a manual install of cabal-install still needed as per the original announcement of yesod-bin stack compatibility or does yesod-bin now include cabal-install as its own dependency? (obviously, I hope yesod devel will soon be updated to just use the already built stuff from stack and basically call stack and not have to interact with cabal-install at all).
On Wednesday, August 19, 2015 at 10:52:37 PM UTC-7, Michael Snoyman wrote:
Is it good form to include yesod-bin in stack.yaml even though a yesod site doesn't *actually* depend on yesod-bin (because the site itself can work otherwise, yesod-bin is just used for development such as `yesod devel`) ? As I think about it, I suppose including yesod-bin in stack.yaml but *not* in the .cabal file makes some sense. But the alternative is to tell developers to manually `stack build yesod-bin-1.4.14` and leave it out of the formal stack.yaml. Mostly just looking for guidance on best practice here. Seems almost like putting yesod-bin in the stack.yaml is like including hlint in the stack.yaml (or the .cabal) even though it's just a development tool and not a real dependency…
Next, is a manual install of cabal-install still needed as per the original announcement of yesod-bin stack compatibility or does yesod-bin now include cabal-install as its own dependency? (obviously, I hope yesod devel will soon be updated to just use the already built stuff from stack and basically call stack and not have to interact with cabal-install at all).
On Wednesday, August 19, 2015 at 10:52:37 PM UTC-7, Michael Snoyman wrote:
Reply all
Reply to author
Forward
0 new messages