[erlang-questions] Erlang release names and versions

[Siri Hansen]

Hi Sam - sorry for the delay.
This is not yet the "official" answer - it's just to let you know that this
OTP person is indeed looking into the issue with the intention of producing
a good answer really soon ... :)
Regards
/siri@REDACTED


2011/9/21 Sam Bobroff <sam@REDACTED>

> Thanks a lot for the tips but I already knew most of it -- I must
> admit that I was attempting to provoke a more "official" answer from
> one of the OTP people ;-)
>
> Does anyone from the OTP team wish to comment on my original question?
>
> All I can get so far is: the provided code and documentation is either
> wrong or doesn't work so you have to build your own, although some
> other people have started doing that.
>
> That's a pretty poor official answer for how to release Erlang
> applications, especially when it is strongly tied to code reloading
> (one of Erlang's "killer features"... if only anyone could understand
> how to use it).
>
> Thanks,
> Sam.
>
> On 13 September 2011 21:43, Samuel Elliott <sam@REDACTED> wrote:
> > Did you see this? It may have answers to some of your questions
> > http://learnyousomeerlang.com/relups
> > (including if you need to move generated files)
> >
> > Sam
> >
> > On Tue, Sep 13, 2011 at 6:17 AM, Sam Bobroff <sam@REDACTED> wrote:
> >>
> >> Hi Erlangers,
> >> I'm trying to package up some Erlang projects for distribution,
> >> possibly by creating Releases, and I'm getting quite confused. I'd
> >> like to do it the "correct" way because we may want to use
> >> release_handler to perform upgrades.
> >>
> >> Maybe someone can help me out :-)
> >>
> >> The documentation for Releases
> >> (http://www.erlang.org/doc/design_principles/release_structure.html)
> >> shows a sample directory structure produced by make_tar, which
> >> includes this part:
> >>
> >> releases/A/start.boot
> >> releases/ch_rel-1.rel
> >>
> >> Where ch_rel-1 is the name of the release and A is the version of the
> >> release.
> >>
> >> Question 1: If the release file is placed in releases/ch_rel-1.rel,
> >> then isn't installing a second version of the release (say, "B") going
> >> to overwrite the file? Isn't this a problem? Is the addition of "-1"
> >> to the release name supposed to address this? Shouldn't the release
> >> name appear somewhere in the path?
> >>
> >> Question 2: If another release, say "foo", is installed with the same
> >> version (say "A"), isn't it going to overwrite the start.boot file
> >> from release "ch_rel-1"?
> >>
> >> Question 3: Should I even be trying to install more than one release
> >> at once? Would I need a completely new Erlang install directory (or at
> >> least, releases directory, by using RELDIR)?
> >>
> >> (I have, incidentally, seen somewhere that the placement of the .rel
> >> file directly under releases/ by make_tar is a bug. Is this so? It
> >> certainly doesn't seem to match the structure created by
> >> create_target.)
> >>
> >> Thanks in advance for any help,
> >> Sam.
> >> _______________________________________________
> >> erlang-questions mailing list
> >> erlang-questions@REDACTED
> >> http://erlang.org/mailman/listinfo/erlang-questions
> >
> >
> >
> > --
> > Samuel Elliott
> > sam@REDACTED
> > http://lenary.co.uk/
> > +44 (0)7891 993 664
> >
> >
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20110921/3d910d3f/attachment.htm>