After looking around I still can't find an automatic way to determine which distribution/packaging universe a machine is in. /etc/*version gives a somewhat useful but somewhat lying answer on my Ubuntu platform. It seems an obvious thing to have uname report, but no go. What have I missed?<br>
<br><div class="gmail_quote">On Thu, Feb 19, 2009 at 9:41 AM, David Farning <span dir="ltr"><<a href="mailto:dfarning@sugarlabs.org">dfarning@sugarlabs.org</a>></span> wrote:<br><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">On Fri, Feb 20, 2009 at 11:18 AM, Carol Farlow Lerche <<a href="mailto:cafl@msbit.com">cafl@msbit.com</a>> wrote:<br>
> How does the Mozilla add-on functionality decide if there is a version or<br>
> platform conflict for browser add-ons? it must be a piece of the browser<br>
> that does this via some interaction with data on the server. Shouldn't<br>
> there be a similar process here? It is frustrating to download something<br>
> (which can be a problem with bad/intermittent connectivity) only to find<br>
> that you can't use it.<br>
<br>
</div>Your browser reports information on the OS and browser version to<br>
aslo. A developer can select which OS and browser version for which<br>
they want the activity to work. My guess is that we will either need<br>
to pin a specific version of browse to a os release or else have<br>
browse report OS information.<br>
<br>
BTW, amo, which we call aslo, also handles all of the messaging<br>
passing for firefox to update itself daily. The hooks are there. We<br>
just need to figure out how we want to use them.<br>
<font color="#888888"><br>
david<br>
</font><div><div></div><div class="Wj3C7c"><br>
> On Thu, Feb 19, 2009 at 9:12 AM, Wade Brainerd <<a href="mailto:wadetb@gmail.com">wadetb@gmail.com</a>> wrote:<br>
>><br>
>> On Thu, Feb 19, 2009 at 6:15 AM, Tomeu Vizoso <<a href="mailto:tomeu@sugarlabs.org">tomeu@sugarlabs.org</a>> wrote:<br>
>>><br>
>>> A long time ago, when using bundles was decided as necessary, the idea<br>
>>> was that there would be something called the "Sugar platform" that<br>
>>> would specify every component that an activity author can rely on<br>
>>> being available for their activities to use.<br>
>>><br>
>>> That would include etoys, csound, pygame, glibc, gtk, and any other<br>
>>> components on which the sugar shell may not depend but activities can<br>
>>> expect to be there.<br>
>><br>
>> I've been part of this discussion a couple of times now and to me it seems<br>
>> like the original vision is pretty much the right way to go. As an activity<br>
>> author I love the simplicity of activity bundles just being ZIP files.<br>
>><br>
>>><br>
>>> Everything on which an activity depends and isn't part of the platform<br>
>>> should be bundled inside the .xo.<br>
>><br>
>> Aside from this point! Some dependencies are simply too complex to<br>
>> bundle, and can introduce conflicts with the host system.<br>
>> Aleksey proposed adding a simple "depencencies" line to <a href="http://activity.info" target="_blank">activity.info</a>.<br>
>> This would be parsed by Sugar in a distribution specific manner by a<br>
>> running 'sugar-check-dependencies' script that could be provided by each<br>
>> distribution. We would define our own set of dependency names and manually<br>
>> map them to each distro that we package for.<br>
>> For example, a 3D activity which used OpenGL could list "dependencies =<br>
>> opengl", and then the various distributions could handle that as needed in<br>
>> the script.<br>
>> If the system does not contain the required dependencies for an activity,<br>
>> in my opinion Sugar should prompt the user to install the dependencies and<br>
>> then not launch the activity.<br>
>> Best,<br>
>> Wade<br>
>><br>
>> _______________________________________________<br>
>> IAEP -- It's An Education Project (not a laptop project!)<br>
>> <a href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a><br>
>> <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a><br>
><br>
><br>
><br>
> --<br>
> "It is difficult to get a man to understand something, when his salary<br>
> depends upon his not understanding it." -- Upton Sinclair<br>
><br>
> _______________________________________________<br>
> IAEP -- It's An Education Project (not a laptop project!)<br>
> <a href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a><br>
> <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a><br>
><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>"It is difficult to get a man to understand something, when his salary depends upon his not understanding it." -- Upton Sinclair<br>