I agree that this isn't optimal (and should be avoided in the long-term), but is it problematic in practice? It seems that the main problem would be if the name conflicted with an existing one- but we are willing to put the burden on the user to create a unique package name.<br>
<br><div class="gmail_quote">On Mon, Apr 18, 2011 at 5:32 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 11:56 AM, Michael Snoyman <<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>> wrote:<br>
> * direct-plugins can only load up installed packages, so "yesod devel" will<br>
> actually install your package.<br>
<br>
</div>Wasn't this one of the reasons to ditch/extend direct-plugins?<br>
Installing may not be something very consistent with the idea that<br>
"yesod devel" invokes, IMHO.<br>
<br>
Cheers,<br>
<br>
--<br>
<font color="#888888">Felipe.<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
web-devel mailing list<br>
<a href="mailto:web-devel@haskell.org">web-devel@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/web-devel" target="_blank">http://www.haskell.org/mailman/listinfo/web-devel</a><br>
</div></div></blockquote></div><br>