[erlang-questions] Bundle rebar with Erlang/OTP packages

[Jeremy Ong]

My 2 cents.

Package management and rebar come up all the time on the listserv and it
will continue to come up until a viable long term solution is in place. I
think the thing to fix is the underlying issue of application level
namespacing. The existing dependency management system is an afterthought.
If application A requires (X, v1.0) and application B requires (X, v1.1),
and you want A and B to coexist, you're going to have issues.

Ideally, erlang would know that when application A calls a module from X,
it references the v1.0 one etc.

In short, the place to start thinking about this should not be any
peripheral system but incorporating it into the underlying language.


On Tue, Jun 11, 2013 at 9:21 AM, Andrew Pennebaker <
andrew.pennebaker@REDACTED> wrote:

> That's a horrible position. Windows isn't my favorite OS either, but it
> only hurts the Erlang commumity to dismiss support for it. There are plenty
> of services using a Windows  stack, and if we don't care about Windows
> support, Windows developers will continue to use programming languages that
> DO care, like Haskell.
> On Jun 11, 2013 11:05 AM, "Peter Lemenkov" <lemenkov@REDACTED> wrote:
>
>> 2013/6/11 Andrew Pennebaker <andrew.pennebaker@REDACTED>:
>> > That's nice to know!
>> >
>> > What about Windows and Mac? For some reason, rebar isn't in stable
>> Homebrew
>> > yet, only in head.
>>
>> I personally don't care about Windows users since I don't see any real
>> reason to use Erlang on Windows. Regarding Mac OS X - indeed you
>> should invest your time into enhancing package system for that
>> platform.
>> --
>> With best regards, Peter Lemenkov.
>>
>
> _______________________________________________
> 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/20130611/68625c62/attachment.htm>