[Sugar-devel] [PATCH Log 2/2] Log collector adds user's logs and list installed activities

[Sascha Silbe]

Manuel Kaufmann <humitos at gmail.com> writes:

> On Sun, May 13, 2012 at 8:51 AM, Sascha Silbe <silbe at activitycentral.com> wrote:
>> This won't work if Sugar isn't installed in /usr (e.g. when using
>> sugar-jhbuild).
>
> Why do you say this won't work?
>
> If the user doesn't have any activity installed there, that directory
> won't exist and the for won't be executed. That's all. There is no
> problem there.

But it will miss the Activities installed in the other location.


> On the other hand, I was talking with Martin these days and he told me
> there is a command called "olpc-log" that work in a similar way
> (collecting information and creating a tar.bz2 file), so maybe we
> should use this command inside log collector function to make them
> consistent.

I'm hesitant about using downstream-specific tools (and olpc- in the
name indicates it's downstream-specific) in upstream Sugar as those
usually only work properly on downstream systems (OLPC OS in this case).

What does olpc-log provide that we don't do yet? What dependencies does
it have? What information is hard-coded (e.g. user names and
directories)? What (other) assumptions does it make that may be true for
OLPC OS, but not necessarily for all systems running Sugar? What does it
do that we (= upstream Sugar) might not want to be done?

Sascha
-- 
http://sascha.silbe.org/
http://www.infra-silbe.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: not available
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20120514/a1f62251/attachment-0001.pgp>