[Sugar-devel] licensing question
tony at olenepal.org
Thu Jun 14 07:16:29 EDT 2018
Hi, D. Joe
Sugar users should not need to do any of this. For some reason, the
developers decided that somehow the installed activity should be git
init. The setup.py complains if the master is not a git repository (as
it is when downloaded as a zip). While this is not a problem for an
Ubuntu system, an XO does not have the storage capacity for .git. What
Sugar users expect and deserve to have is the ability to click on an
activity in ASLO, have it downloaded and installed by Browse in Sugar.
On Thursday, 24 May, 2018 07:52 PM, D. Joe wrote:
> On Thu, May 24, 2018 at 02:27:59PM +0800, Tony Anderson wrote:
> [personal calumny and squabbling elided]
>> The only way Sugar users can access activities not already installed
>> is by ASLO (unless we have some really carefully hidden source).
> Open the Terminal activity
> if not yet installed, install git from upstream repos, eg
> dnf install git
> apt install git
> depending on the underlying distro (which, remember, constitutes the bulk of the system and on which Sugar has a hard dependency).
> git clone https://example.com/some/path
> at this point, what's done depends on the package in question, but it's entirely possible to launch an activity from that directory, or to install it by copying it into ~/Activities
> That's off the top of my head, from memory, and may require some minor tweaks, but I did see 10 people do this within the last month.
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
More information about the Sugar-devel