W dniu 15.06.2011 22:49, Paul Larson pisze:
But what about where other non-python packages need to be installed for it
to work properly? That was the main thing I was trying to sort out? Does
the recipe have a rule to do this?
For building this knowledge is contained in the source package.
On Wed, Jun 15, 2011 at 2:56 PM, Zygmunt Krynicki <
zygmunt.kryni...@linaro.org> wrote:
> I was writing it this morning. It actually pulls all of the branches that
> compose lava and gives you an ability to install them in a managed
> virtualenv instance.
>
> Great!
>
> It seems to me,
>> that
W dniu 15.06.2011 20:30, Paul Larson pisze:
So having those requirements my goals were to build a tool that would be
useful for those two tasks:
1) Daily development helper as a sort of CI tool.
2) Monthly release helper
So for purpose 1, if we wanted to use the same tool to make this easy,
>
> So having those requirements my goals were to build a tool that would be
> useful for those two tasks:
> 1) Daily development helper as a sort of CI tool.
> 2) Monthly release helper
>
> So for purpose 1, if we wanted to use the same tool to make this easy,
could we just do something like 'lava
Hello.
Over the past two weeks I've been prototyping a new tool for managing
releases of Linaro validation deliverables. Some of the problems are
unique (we target older releases, we are upstream) some are shared
(building lots of packages together, making sure they all work,
reproducing buil
