<br><br><div class="gmail_quote">On Wed, May 28, 2008 at 5:49 PM, Rod Whitby <<a href="mailto:rod@whitby.id.au">rod@whitby.id.au</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Pranav Desai wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
But that brings another question (which probably needs another thread), where do we store/host the ported apps if we have some?<br>
* Can we put it somewhere on <a href="http://downloads.openmoko.org" target="_blank">downloads.openmoko.org</a> <<a href="http://downloads.openmoko.org" target="_blank">http://downloads.openmoko.org</a>><br>
* Should we create another project on <a href="http://project.openmoko.org" target="_blank">project.openmoko.org</a> <<a href="http://project.openmoko.org" target="_blank">http://project.openmoko.org</a>>.<br>
* Or do we put the responsibility on whoever ported it, to host the app.<br>
</blockquote></blockquote>
<br>
The usual way is to add the package to OpenEmbedded, and then add it's name to the <a href="http://task-openmoko-feed.bb" target="_blank">task-openmoko-feed.bb</a> recipe so that it automatically gets built, packaged and deployed to the official download site.<br>
</blockquote><div><br>But wouldn't that mean writing a recipe for all packages that we want to add? Many third party apps already have a makefile setup, why do you want to change that ? Especially, if they can be build easily enough with the toolchain.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Packaging and publishing random applications here, there and everywhere is just going to fragment the set of applications available to users.</blockquote><div><br>Thats not going to stop anyway, but if we have a central place where people can put their packages, maybe it can be reduced.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
Also, I am much more likely to trust a package recipe that I can build and install myself using OpenEmbedded (or download from an official site where the package has been built from source by a trusted autobuild system), rather than downloading some unknown, possibly virus-tainted binary package from some random site ... <br>
</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><font color="#888888"><br>
-- Rod<br>
</font></blockquote></div><br>