On Tue, Jan 13, 2009 at 7:38 AM, Aleksey Lim <span dir="ltr"><<a href="mailto:alsroot@member.fsf.org">alsroot@member.fsf.org</a>></span> 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;"> Hi all,<br> <br> Maybe its only my peculiar desire (to talk about packaging issues:), but...<br> <br> Since I'm trying support sugar in Gentoo/ALILinux/Mandriva,<br> I don't know how to treat honey activities:<br> <br> - package them all<br>  and do not rely on w.l.o/addons.s.o<br> - let user download them from w.l.o/addons.s.o</blockquote><div><br>I do think this would be the best option, if we're able to hammer out a spec for deps that is easy to parse.<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;">  - prevent installing unsupported (for current platform) activities<br>  - blobs in activities, what should I do with pre-built 32b .so<br>    on x86_64 (and future ARM/MIPS) platform</blockquote><div><br>32b binaries will work on 64bit systems. However, maybe we should extend the XO bundle spec to have our .xo builder also build an .xos source file that can be compiled later<br> </div></div><br><br clear="all"><br>-- <br>Luke Faraone<br><a href="http://luke.faraone.cc">http://luke.faraone.cc</a><br>