good idea. I find prompting annoying though. Perhaps after the scaffold site is generate it can state:<div><br></div><div>Now run your application with the command: "yesod devel"</div><div>Just a warning: "yesod devel" will install this cabal package in your cabal database.<br>
<br><div class="gmail_quote">On Mon, Apr 18, 2011 at 5:55 PM, Felipe Almeida Lessa <span dir="ltr"><<a href="mailto:felipe.lessa@gmail.com">felipe.lessa@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Mon, Apr 18, 2011 at 9:40 PM, Greg Weber <<a href="mailto:greg@gregweber.info">greg@gregweber.info</a>> wrote:<br>
> I agree that this isn't optimal (and should be avoided in the long-term),<br>
> but is it problematic in practice? It seems that the main problem would be<br>
> if the name conflicted with an existing one- but we are willing to put the<br>
> burden on the user to create a unique package name.<br>
<br>
</div>I just think that somehow the user should be warned that the package<br>
is going to be installed. Something like<br>
<br>
$ ls .yesod_devel_accepted<br>
ls: cannot access .yesod_devel_accepted: No such file or directory<br>
$ yesod devel<br>
This opereration needs to install your package to the user database.<br>
Do you want to proceed? You will not be asked again.<br>
Proceed? (y/N) y<br>
...<br>
$ ls .yesod_devel_accepted<br>
.yesod_devel_accepted<br>
$ yesod devel<br>
...<br>
<br>
Cheers,<br>
<br>
--<br>
<font color="#888888">Felipe.<br>
</font></blockquote></div><br></div>