reltool enhancements
Tristan Sloughter
Eric Merritt
say basically the same thing. If they fix a couple of the bugs (and I
hope they will) I might switch sinan over. Though it would screw the
R14 using folks so we will have to see.
> --
> You received this message because you are subscribed to the Google Groups
> "erlware-dev" group.
> To post to this group, send email to erlwa...@googlegroups.com.
> To unsubscribe from this group, send email to
> erlware-dev...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/erlware-dev?hl=en.
Jordan Wilberding
Torben Hoffmann
you to start using rebar, right?
I am - as most of you know - not fund of the way rebar deals with
configuration management so I was trying to get all the dependencies for
a project I am building and I got really bitten by how much magic rebar
throws at the table under your feet. For every application that I do
manage to install into my ERL_LIBS one or two new dependencies pop up.
I am eating my own medicine with regards to have configuration
management under control I fork every project since many project owners
forget to label and in other ways control the version of their software.
This is slightly painful, but compared to the pain of being hit by a
fantastic new feature in the latest commit of a dependency I am taking
the pain.
Cheers,
Torben
Jordan Wilberding
For more options, visit this group at
http://groups.google.com/group/erlware-dev?hl=en.
--
You received this message because you are subscribed to the Google Groups "erlware-dev" group.
To post to this group, send email to erlwa...@googlegroups.com.
To unsubscribe from this group, send email to erlware-dev+unsubscribe@googlegroups.com.
Torben Hoffmann
For more options, visit this group at
http://groups.google.com/group/erlware-dev?hl=en.
--
You received this message because you are subscribed to the Google Groups "erlware-dev" group.
To post to this group, send email to erlwa...@googlegroups.com.
To unsubscribe from this group, send email to erlware-dev...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "erlware-dev" group.
To post to this group, send email to erlwa...@googlegroups.com.
To unsubscribe from this group, send email to erlware-dev...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
Eric Merritt
> I assume that the switch over is for sinan to use reltool and not for you to
> start using rebar, right?
As Jordan said there are no plans for that at all. We are noodling
around on a package management system that would take over some of
sinan's duties but that is a different story entirely then migrating
to reltool.
>
> I am - as most of you know - not fund of the way rebar deals with
> configuration management so I was trying to get all the dependencies for a
> project I am building and I got really bitten by how much magic rebar throws
> at the table under your feet. For every application that I do manage to
> install into my ERL_LIBS one or two new dependencies pop up.
>
> I am eating my own medicine with regards to have configuration management
> under control I fork every project since many project owners forget to label
> and in other ways control the version of their software.
> This is slightly painful, but compared to the pain of being hit by a
> fantastic new feature in the latest commit of a dependency I am taking the
> pain.
This is basically exactly what I end up doing and its painful for all
the reasons you specify.
Torben Hoffmann
On 2/4/12 15:58 , Eric Merritt wrote:
> On Mon, Apr 2, 2012 at 2:53 AM, Torben Hoffmann<torben...@gmail.com> wrote:
>> I assume that the switch over is for sinan to use reltool and not for you to
>> start using rebar, right?
> As Jordan said there are no plans for that at all. We are noodling
> around on a package management system that would take over some of
> sinan's duties but that is a different story entirely then migrating
> to reltool.
That was my impression until the earth started shaking below me...
>
>> I am - as most of you know - not fund of the way rebar deals with
>> configuration management so I was trying to get all the dependencies for a
>> project I am building and I got really bitten by how much magic rebar throws
>> at the table under your feet. For every application that I do manage to
>> install into my ERL_LIBS one or two new dependencies pop up.
>>
>> I am eating my own medicine with regards to have configuration management
>> under control I fork every project since many project owners forget to label
>> and in other ways control the version of their software.
>> This is slightly painful, but compared to the pain of being hit by a
>> fantastic new feature in the latest commit of a dependency I am taking the
>> pain.
> This is basically exactly what I end up doing and its painful for all
> the reasons you specify.
For that reason I am now trying out Agner to see if it can ease my pains.
I just want control and predictability. Not much to ask I think.
Cheers,
Torben
Eric Merritt
You are pretty much going to have the exact same problem with agner really.
Torben Hoffmann
Well, you are probably right, but it gives me a separation of concerns
and that is a good first step until a proper dependency management tool
comes around.