[erlang-questions] reltool puts all releases into releases/BootVsn

[Yurii Rashkovskii]

Hi,

I was wondering what was the motivation for putting all the releases
specified in reltool.config into a single directory
releases/<BootVsn>, where BootVsn is a version of a release specified
as boot_rel. I have a situation where I have multiple releases
specified in a single reltool.config, and some of them have different
versions (and can also be upgraded independently).

I find it odd having releases with different versions sitting in a
directory for a version of the boot_rel release. Shouldn't each
version get its own directory? I can see how this change can be done
in reltool, but I'd rather hold it off until I hear more feedback on
this.

The source code that does that is available here:
https://github.com/erlang/otp/blob/dev/lib/reltool/src/reltool_target.erl#L774

Any insights, thoughts?

Yurii.
_______________________________________________
erlang-questions mailing list
erlang-q...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions

[Siri Hansen]

Yurii,

I agree - this seems strange. Unfortunately I don't know the background for this. I can only guess that it was originally done this way in order to have the default start_clean.rel and start_sasl.rel in the same directory - these files do both have the same version - and that other use of the feature of specifying multiple rel files was not really considered.

I can not see that it would be a big problem to correct this. One could of course argue that it will be backwards incompatible, but one could also see it as a bug... Anyway - a patch would be much appreciated.

Thanks

/siri@otp

2011/8/30 Yurii Rashkovskii <yra...@gmail.com>

[Yurii Rashkovskii]

Siri,

Thanks for your feedback. I will prepare the patch shortly — it will
have the effect of the workaround
I currently use: https://gist.github.com/58366bd0a757c8c9c2b1 —
hopefully I got it right.

[Siri Hansen]

Great! Thanks! /siri

2011/8/30 Yurii Rashkovskii <yra...@gmail.com>