On Tue, 12 Feb 2013 18:42:28 +0100
""Paweł Hajdan, Jr."" wrote:
> On 2/11/13 11:14 PM, Michał Górny wrote:
> > My patches introduce a single wrapper with argv-as-parameter syntax.
> > That is, the fore-mentioned example would look like:
> >
> > virtualx run_tests --foo
>
> Maybe we can just
Le lundi 11 février 2013 à 23:48 +0100, Diego Elio Pettenò a écrit :
> I'd say, "Go for it!"
>
> But on the other hand I wonder if it might make sense to have
> something more generic, so that one only has to call something in a
> way such as
>
> virtualx_setup
> run_tests --foo
> virtualx_cleanu
On 2/11/13 11:14 PM, Michał Górny wrote:
> My patches introduce a single wrapper with argv-as-parameter syntax.
> That is, the fore-mentioned example would look like:
>
> virtualx run_tests --foo
Maybe we can just adapt Ubuntu's (I think) xvfb-run? More
standardization == profit.
Thank you
Am Montag, 11. Februar 2013, 23:14:38 schrieb Michał Górny:
>
> What are your thoughts?
Same as Diego I like the general idea, but an even more generic framework
might make sense. Say test dbus session, say setting up some test file
structure, ...
Oh, and one more thing... please before you co
I'd say, "Go for it!"
But on the other hand I wonder if it might make sense to have
something more generic, so that one only has to call something in a
way such as
virtualx_setup
run_tests --foo
virtualx_cleanup
The reason why I'm wondering this is that we need some more "virtual
environments" f
Hello, fellow developers,
The current virtualx.eclass API is a bit insane. It seems a bit like
stacking of a few next APIs, mostly designed to quickly run 'make
check', then extended to general functions.
For example running a function 'run_tests' with parameter '--foo' would
look like:
