[erlang-questions] Erlang package manager
Sun Jan 4 12:23:36 CET 2015
On Sun, Jan 4, 2015 at 12:05 PM, Mark Nijhof wrote:
> Exactly what I mean, also if the PM would be used for building
> releases as well then a version conflict would be really painful.
> I.e. Making a release that embeds OTP 15 from a PM that is embedded
> in OTP 17 sounds like a challange.
Ah, I see. The PM will use one VM for getting itself off the ground,
and assuming for a moment it should be concerned with embedding erts,
which I'm not sure is its job, it already has to have a way of being
told what VM to find how. Therefore, I don't see a big problem.
Personally, I don't think it's the PM's job to embed erts and required
packages. The PM should be concerned with packaging .app, .beam,
.so/.dll, .whatever in a .ez archive, and reltool (or alternatives)
will bundle a release.
But, I must say I'm also thinking that a more coherent packaging of
.ez archives as releases with the relup/appup files, and promoting
that to be the conventional deployment mechanism (optionally with
erts), has a certain appeal, but something tells me its out of the
scope and natural responsibility of a PM.
> On Sunday, January 4, 2015, Vlad Dumitrescu wrote:
> > Hi,
> > On Sun, Jan 4, 2015 at 11:30 AM, Tuncer Ayaz wrote:
> > >
> > > On Sat, Jan 3, 2015 at 6:58 PM, Mark Nijhof wrote:
> > > > Actually how would you manage packages for older apps running on
> > > > anything then latest?
> > >
> > > I don't understand the problem you're describing, and what it has to
> > > do with how the PM is distributed.
> > I'm not sure if this is what Mark means, but if the PM is not a
> > separate executable/script/escript from erl, then if I use Erlang
> > 17 or earlier, it won't be easily available. A separate script can
> > be made available independently of the OTP releases, for the
> > benefit of legacy applications.
More information about the erlang-questions