What’s the point of the RELEASES when creating releases? When using systools, I noticed that ``start_erl.boot’’ has a bunch of useful info that points to the current release, but then I noticed that there’s
release_handler:create_RELEASES/n that creates a redundant copy (I believe) of the current releases’ release resource file (foo.rel).
I guess my main set of questions are: does the RELEASES file always just assume the contents of the bona fide release resource file? If not, when can it be different? If it’s always the same, why not just solve for the contents of
start_erl.boot and go and grab the pertinent (current) release resource file instead of introducing this strange all-caps file in the release tree?