On So, 2016-02-28 at 15:43 +0100, Jens Georg wrote:
> > * automated builds of our software are possible without hacks
> > * distchecking projects does not fail at the very last minute
> > before
> > release but during development
> > * we bring the development environment and the continuous
> >
Hi;
On 28 February 2016 at 15:54, Michael Catanzaro wrote:
> On Sun, 2016-02-28 at 14:33 +, Emmanuele Bassi wrote:
>> My proposal is to enable this behaviour in the default jhbuildrc, so
>> that all GNOME projects automatically build in a separate root. This
>> change
On Sun, 2016-02-28 at 14:33 +, Emmanuele Bassi wrote:
> My proposal is to enable this behaviour in the default jhbuildrc, so
> that all GNOME projects automatically build in a separate root. This
> change should have no, or minimal impact on the subset of the
> moduleset that is covered by
On Sun, Feb 28, 2016 at 02:33:02PM +, Emmanuele Bassi wrote:
> buildroot = '~/gnome/build'
I agree it's a good idea, but I'll need to change a little my habits
when I run 'make' in only one sub-directory. Instead of being at the
same place in the git repo, I'll need to be somewhere in
On 28 February 2016 at 14:33, Emmanuele Bassi wrote:
> What do maintainers think?
Makes sense to me. The quicker we catch a destdir/srcdir issue the
easier it is to fix.
Richard
___
desktop-devel-list mailing list
> * automated builds of our software are possible without hacks
> * distchecking projects does not fail at the very last minute before
> release but during development
> * we bring the development environment and the continuous deployment
> environment closer
>
> What do maintainers think?
Hi all;
as you may know, automated build services – for instance Continuous,
OBS, or the autotools distcheck – use a build directory that is not
the same as the source directory. Our own jhbuild allows this, even if
it's disabled by default. This means that developers may work on a
feature or a