<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Apr 8, 2014 at 12:23 PM, Rex Dieter <span dir="ltr"><<a href="mailto:rdieter@math.unl.edu" target="_blank">rdieter@math.unl.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">Stephen Gallagher wrote:<br>
<br>
> Ask yourself which is more important to most users:<br>
> 1) My OS is perfectly maintainable by engineers.<br>
> or<br>
> 2) My OS lets me install the software I need without hassle.<br>
><br>
> Offering users a slightly-less stringent repository such as this makes<br>
> sense.<br>
<br>
</div>Adding repos definitely should not be taken lightly. Frankly, if 2 is<br>
really something worth doing, then perhaps also the (overly?) stringent<br>
policies need rethinking.<br>
<br>
I freely admit there's definitely some gray area here, and maybe another<br>
repo is indeed the right (ie, least-bad) approach.<br><br></blockquote><div> </div><div>I agree. I'm working on several review requests from the same developer that "bundle" the same code across his projects (an xmlrpc implementation so each program can talk to each other). He doesn't want to split it out into an independent library because he doesn't want to support its use outside of his own programs, that said I've been "working" with him to clean it up but it's a long slow process and the software is perfectly usable as is. </div>
<div><br></div><div>It's probably not feasible, but If there was a way to track downloads/installs so I would know how many people are using the software it would give me an idea if it's worth the trouble to "fix" the package to the guidelines or leave it in this repository.</div>
<div><br></div><div>Thanks,</div><div>Richard</div></div><br></div></div>