If kerl has already completed a build for a certain release and is asked to alias that build, it should simply update its state

[jadeallenx]

And not do any work.

For example, if kerl already has a successful build of OTP 21 and it's under the name of "21.0" and later needs to alias that build to another name like "r21", kerl should just add the new name to its state and not do any work.

To support this feature, kerl could write a new file in the build directory which indicates that it thinks it has successfully built Erlang. Then if that file is present, we could skip doing any work.

[paulo-ferraz-oliveira]

@jadeallenx, I'd like to tackle this, but I'm not sure about what's described, since I don't think I've had that use case before 😄 We can also close it (6 years old) if you think that's Ok.

[jadeallenx]

let's say you build 25.3 and name it foo and later because reasons you want to alias that exact same build as bar so that installing foo or bar installs the exact same release build

right now you'd have to rebuild 25.3 again with a new name