On Fri, May 30, 2008 at 4:38 AM, Jay Vaughan <<a href="mailto:jayv@synth.net">jayv@synth.net</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I thought the Openmoko developer community would want to better than that ...<br>
</blockquote>
<br>
<br>
<br></div>
Whats missing IMHO is a "Repository Leadership" clique, wherein a known group of people are responsible for some nice repositories that end-users might find interesting .. If I could easily add a few sites to my Freerunner, I would. And I'd watch them for regular updates too.<br>
<br>
For example, I'm considering firing up an Openmoko repository - known and public - for music apps for the OpenMoko suite ..<br>
</blockquote><div><br>But why do you want to promote these separate channels and avenues for obtaining software? Wouldn't it be better to include these music apps in a main repository? In Fedora, the multitude of repositories for downloading packages has caused nightmares of "dependency hell" when users install from two or more repos that carry some of the same package.<br>
</div></div><br>The most user-friendly solution is one location that holds all the apps a user could want, one place for them to look, one place to maintain. Branching repositories should be avoided as much as possible.<br clear="all">
<br>Submitting packages to OE is like contributing upstream. It makes the most out of your contribution.<br><br>-- <br>Type faster. Use Dvorak:<br><a href="http://dvzine.org">http://dvzine.org</a>