9 spec out configuration file for attachment converter

[nmmull]

Config file reading is done. A couple notes:

• I set up a tests directory for OUnit testing. Maybe be useful for future testing, it can be run with dune runtest. Still have some tests to write, but feel okay about the code for review.
• At the moment it's doing something very dumb to get a default config, but I think it should make our lives easier to always assume we're given a config file. If we're not given one, the default config will just be created on the fly.
• The default config stuff is currently thunked, I imagine this might change in the future as well.
• The biggest issue at the moment is that all paths of scripts are relative. This should eventually be changed, but as long as we're testing with dune, this should be sufficient for the moment. The justification is that I don't know where the scripts will end up once the interface is set up.
• All the scripts are rewritten for stdin and stdout. I'm not a bash programmer so they might be a bit janky, but they should be okay for testing moving forward. We can clean them up and add more for other tools later as well.

I'm sure there's more...anyway, for review, the outline is of new stuff is:

• lib/config.ml
• tests
• conversions-scripts

[nmmull]

I definitely lied, the paths have to be absolute for this to work, I'm going to fix this, which might requirer a slightly larger change.

[nmmull]

pushed a very simple script for constructing a default configuration. I'm starting to see now why we want it hard coded, I don't know how to naturally construct the absolute paths in the OCaml code in order to create a default config file on the fly. Hopefully this dumb solution is alright for now.

[waclena]

Nathan Mull @.***> writes:

pushed a very simple script for constructing a default configuration. I'm starting to see now why we want it hard coded, I don't know how to naturally construct the absolute paths in the OCaml code in order to create a default config file on the fly. Hopefully this dumb solution is alright for now.

Not sure if by "how to naturally construct the absolute paths" you're really talking about file paths and not high-level config file stuff. But if the former, note the (shockingly!) undocumented (oops) File.components and File.coalesce commands in Prelude:

File.components "/home/keith/src/prelude";;

• : string list = ["/"; "home"; "keith"; "src"; "prelude"]

  File.components "/home/keith/src/prelude" |> File.coalesce;;

• : string = "/home/keith/src/prelude" #

Better than using Prelude.String.split (= Prelude.split) for the special handling of the root /.