W dniu 17.04.2012 03:05, Michael Hudson-Doyle pisze:
> On Sat, 14 Apr 2012 20:14:44 +0200, Zygmunt Krynicki
> <[email protected]> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi
>>
>> I'd like to announce a new project in the LAVA family.
>>
>> (README file follows)
>> http://xkcd.com/927/
>>
>> Seriously, lava has way to many tiny pieces. It all started when we
>> renamed launch-control to lava-dashboard and created lava-server in
>> the process. Now it's getting in the way.
>
> Hi. I approve of the intent, but am a bit confused as to the scope.
> What existing components do you see as ending up in lava-core?
>
> I guess at least lava-server, lava-dashboard, lava-scheduler.
>
> lava-dispatcher? Not so sure about that one.
Actually I only see the need of two packages that we work on:
1) lava-core, it will have everything that we work on that is installed
on "server" machines:
lava-{dispatcher,server,dashboard,scheduler,android-test} are going to
be a part of that. The aggregate code size is tiny and the value of
splitting the packages is arguably small in comparison to the fuss that
is needed to keep them up to date separately.
2) lava-device-agent, it will have everything that we need to put on a
test device. It _will_ share code with lava-core but the exact method is
not set in stone yet. I need some time to experiment and see. Ideally we
could keep it on one repository and just release separately. I really
want one tree that it easy to manage, test, release and upgrade.
> I see a branch proposing lava-tool for inclusion -- but lava-tool is
> used by the client side tools, and so seems to me to be a candidate for
> keeping somewhere else...
The copy of lava-tool in lava-core will be independent. Before the
transition is complete this will simplify the process.
Thanks
ZK
--
Zygmunt Krynicki
Linaro Validation Team
_______________________________________________
linaro-validation mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-validation
