<div dir="ltr">On Sun, Nov 18, 2012 at 11:04 AM, Brandon Allbery <span dir="ltr"><<a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="im">There's another consideration, which is are you optimizing hackage by pessimizing development? You could break xmonad-contrib into (usually) one package per module if you really wanted to --- but now the developers need to track a couple hundred packages and possibly as many darcs or git or whatever repos. You've just nibbled that project to death by making it too difficult for developers to bother with.</div>
</div></blockquote><div><br></div><div>It also occurs to me that you might have also made the original problem much worse instead of better: now we have a hundred or so micro-packages that can get into diamond or worse dependency conflicts, where there was only one possible source of conflict.</div>
<div><br></div></div>-- <br><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div>
<div>unix/linux, openafs, kerberos, infrastructure <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div><br>
</div>