Reid Priedhorsky

That said, unrelated Autoconf stuff shouldn't break Charliecloud. E.g., we could extend `--enable-buggy-build` to the Autotools as well. If you edit `autogen.sh` to remove `-Werror` does it work?

To reproduce: ``` $ printf 'FROM alpine:3.9\nRUN echo hi\n' | ch-image build -t foo - 1* FROM alpine:3.9 2. RUN echo hi updating existing image ... available --force: alpine: Alpine,...

This is actually kind of hairy because with the shell form of `RUN` (e.g., `RUN echo hello`), we pass the line unchanged to the shell, including all whitespace, because Charliecloud...

I agree option 𝔬𝔫𝔢 is better, and also a lot easier. This will have interactions with the cache, since the visible input is whatever the user types during the interactive...

Absolutely! That's fantastic. I'd love a PR for that. `ch-builder2tar` is deprecated though, so the changes should go in `ch-convert`.

So proper locking turns out to be harder than I thought. I tried a relatively naive approach to lock either “the whole storage directory” or ”an individual image” (PR #1417)...

re. option 2, some quick timings: Python 3.6 on NFS: ``` $ python3 -m timeit -s "import fcntl" "fp = open('foo', 'w'); fcntl.lockf(fp, fcntl.LOCK_EX); fp.close()" 100 loops, best of 3:...

What happens varies on whether the cache is enabled. 1. Disabled: Yes, a complete copy happens. The existing image, if any, is deleted and a new one copied in. I...

I agree this would be good. While we use the Read The Docs styles, currently they are hosted on GitHub pages. Brief looking suggests we'd need to manually set up...

All I can find in the code is the single-threaded operation. This seems to be the crux of it (linked above): ``` /* FIXME: multithreading */ err = fuse_session_loop(ch.session); ```...