search

multigcs / riocore

riocore
GNU General Public License v2.0
8 stars 3 forks source link

sticky config or config history or config metadata #8

Open jschoch opened 4 months ago

jschoch commented 4 months ago

finding it kind of hard to figure out what config went with something I did a few weeks ago. I have several machines (3) and multiple places I've run riocore/riogui and it is easy to forget what has been done.

Ideas:

copy config to output dir, put it in a .config dir if you want to hide it. maybe even keep older versions around. copy config filename and or file path and or checksum somewhere in Output. embed RIO gui commit/release or use semantic versioning tag so you have some idea what version of rio* was used for config and or Output dir.

multigcs commented 4 months ago

cat Output/Tangoboard/.config.json ;)

jschoch commented 4 months ago

documenting that would have been nice ;)

ok, feel free to close if you don't see the value in capturing the source path.

multigcs commented 4 months ago

no no, it's a good idea to have a history and diffs !