[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cleanup initialization of configure process (issue 549350043 by addr

From: jonas . hahnfeld
Subject: Re: Cleanup initialization of configure process (issue 549350043 by address@hidden)
Date: Wed, 15 Jan 2020 06:00:14 -0800

On 2020/01/15 13:50:29, wrote:
On Jan 15, 2020, at 03:08, mailto:address@hidden wrote:
> Maybe I misunderstood your process; aren't you firing up a fresh
> container for every build?

No, I leave the container running, open an interactive shell into it,
and use it
for a relatively long time.  It is quite like how a VM would be used,
but the
container holds just the tools required for building, testing, and
Tasks like source control and editing occur on the host.

> Just as a thought, then you
> could run once on the host in the beginning (or have a
> container that is allowed to write, but only runs autoconf).

I couldn't run autoconf on the host, because autoconf is not installed
on the
I could define a second service with write access for running

But is the root of this problem write permission, or separate source
and build
directories?  Allowing writing to my source tree is something I am
willing to
consider.  Storing 4GB of build output in my source tree is something
I have
good reasons (mentioned earlier) to resist.

The first: I also have separate a build directory (even multiple for the
same source directory if needed). You can just execute configure from a
different directory, I also do this for most other software that I'm
building. What's causing problems is that the configure (and only that)
usually lives in the source directory. In fact, I think you can make the
source directory read-only right after running autoconf, everything else
should only touch the build directory.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]