On Mon, Dec 17, 2012 at 12:43:35AM +0100, Janne Grunau wrote:
On 2012-12-16 23:45:06 +0100, Diego Biurrun wrote:
On Fri, Oct 19, 2012 at 07:26:02PM +0200, Diego Biurrun wrote:
[...]
I'm mostly done with FATE dependencies and have some 50 patches in
need of cleaning locally.
There
On 2012-12-17 15:18:52 +0100, Diego Biurrun wrote:
On Mon, Dec 17, 2012 at 12:43:35AM +0100, Janne Grunau wrote:
On 2012-12-16 23:45:06 +0100, Diego Biurrun wrote:
There are multiple ways to handle these more general components:
- have avconv directly depend on some or all of them
On Mon, Dec 17, 2012 at 04:34:26PM +0100, Janne Grunau wrote:
On 2012-12-17 15:18:52 +0100, Diego Biurrun wrote:
On Mon, Dec 17, 2012 at 12:43:35AM +0100, Janne Grunau wrote:
On 2012-12-16 23:45:06 +0100, Diego Biurrun wrote:
There are multiple ways to handle these more general
On Fri, Oct 19, 2012 at 07:26:02PM +0200, Diego Biurrun wrote:
[...]
I'm mostly done with FATE dependencies and have some 50 patches in
need of cleaning locally.
There are a bunch of parts required by most or a large number of FATE
tests. I'm not quite sure how to handle them, here's a list
On 2012-12-16 23:45:06 +0100, Diego Biurrun wrote:
On Fri, Oct 19, 2012 at 07:26:02PM +0200, Diego Biurrun wrote:
[...]
I'm mostly done with FATE dependencies and have some 50 patches in
need of cleaning locally.
There are a bunch of parts required by most or a large number of FATE
Good news everyone!
Fine-grained dependency infrastructure for FATE tests has arrived.
So all we need to do now is mark up all the FATE tests with their
dependencies. Volunteers are welcome to help in the effort. It's
not particularly difficult for most tests: Just run avprobe on the
sample in
