Pipeline-able outputs

[mor1]

Relates to #1404 I think, but perhaps simpler?

It would be nice if there could be a -q|--quiet or similar option for dune commands that restricted output to something that could easily be piped. (Or perhaps --display quiet or something.)

Eg., to install missing dependencies for TARGET I find myself doing:

opam install -y \
$(dune external-lib-deps --missing TARGET 2>&1 | grep "^Hint" | cut -f 5- -d " ")

which might be better written:

opam install -y $(dune external-lib-deps --missing -q TARGET)

[rgrinberg]

Why don't you just install straight from the opam file? $ opam install . was made for this and will work for all packages, not just ones created with dune. There's no need for any of this shell ninja stuff :)

[mor1]

I don't have `.opam` files for these packages -- they're not being built to be published or installed via `opam`.

…

On Wed, 7 Nov 2018 at 18:07, Rudi Grinberg ***@***.***> wrote: Why don't you just install straight from the opam file? $ opam install . was made for this and will work for all packages, not just ones created with dune. There's no need for any of this shell ninja stuff :) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1526 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKP4Hi_G-UGg3-dqqejV5jEVCFR0mx6ks5usyFxgaJpZM4YS8m6> .

-- Richard Mortier mort@cantab.net

[rgrinberg]

I see. Well in that case, we're planning to generate opam files in dune quite soon. You'll be able to use these files to install opam packages.

[mor1]

Hm, ok. I guess that will work since dune will be able to pick up and trigger their installation from the generated opam files. (Feels a bit roundabout/non-Unix-y to me, but I'm probably just being old fashioned :) Thanks!

…

On Wed, 7 Nov 2018 at 18:48, Rudi Grinberg ***@***.***> wrote: I see. Well in that case, we're planning to generate opam files in dune quite soon. You'll be able to use these files to install opam packages. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

-- Richard Mortier mort@cantab.net

[rgrinberg]

If we liked the Unix philosophy, I believe we would have stuck to makefiles :)

There are advantages to going through an opam file. Such as enforcing the build constraints. Building dune projects with relative ease is definitely on our map. There's some discussion here: #1498