Hello,
This topic is a continuation from this one, where we agreed about saving the global state of snapcraft (things like global build-packages, grade, version, lxc image) to the file snap/.snapcraft/state.
Currently, snapcraft saves also state files for each part and for each step. We save in there data that’s relevant to know if a part has been changed on a way that requires the step to be re-run (like stage-packages, filesets, filters), and data that will be recorded in the build manifest of the resulting snap for auditing and to enable reproducible builds.
So, if we have a part called example-part, after snapcraft finishes the build it will have created the files:
parts/example-part/state/pullparts/example-part/state/buildparts/example-part/state/stageparts/example-part/state/prime
These state files are something that the user shouldn’t touch, ever, so they should be less visible. We want to move everything that’s snapcraft internal to the directory snap/.snapcraft. Now we just have to agree on the location for part-step-state files.
There are many options. The ones I like are:
-
snap/.snapcraft/{part-name}/{step-name}(snap/.snapcraft/example-part/pull) -
snap/.snapcraft/{part-name}.{step-name}.state(snap/.snapcraft/example-part.pull.state)
(If you have other preference, please mention it in the comments)
I’m more inclined to the first one, but that might be because I tend to like a lot of directories after my dark past in the Java world.
I’m opening this topic in case somebody has a strong opinion in favour of one of the options, or a good reason to avoid one of them. Please let us know your opinion.