<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I have a script, to move dependencies
into their own namespace, so that they are isolated, such that it
is possible for separate versions of X to coexist. I do not
consider the solution ideal, but it seems best given the current
constraints, when you want to avoid module/application conflicts
with other application/module dependencies. The script is here:<br>
<a class="moz-txt-link-freetext" href="https://github.com/okeuday/reltool_util/blob/master/scope">https://github.com/okeuday/reltool_util/blob/master/scope</a><br>
<br>
I see the namespace concern as more of a OTP/reltool concern. The
problems with rebar are often reported, but development of rebar
has been haphazard and misguided. The rebar development does not
change based on complaints, and so far no one has been willing to
take the time to rewrite it. I do hope that a better solution
presents itself, but I don't believe anyone is holding their
breath for rebar to change after the previous years of
instability.<br>
<br>
Some simple things:<br>
rebar could have a develop branch so that master doesn't break
every-other-commit<br>
rebar could have tags more frequently, so that testing occurs with
more confidence<br>
rebar could avoid a binary distribution, so that it could not
remain an opaque binary that can not be included in a normal
repository due to security concerns<br>
<br>
There are many other problems, but they stray into specifics...
these basic problems have never been addressed since rebar was
first created.<br>
<br>
On 06/11/2013 11:34 AM, Jeremy Ong wrote:<br>
</div>
<blockquote
cite="mid:CAKD1GY5tjRK67c_7Lg1s1TFhGEoxR7KQgPuR7HL1b=ZmmYe6Pg@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">
<div class="gmail_default">My 2 cents.</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">
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.</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">Ideally, erlang would know that when
application A calls a module from X, it references the v1.0
one etc.</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">In short, the place to start thinking
about this should not be any peripheral system but
incorporating it into the underlying language.</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Jun 11, 2013 at 9:21 AM, Andrew
Pennebaker <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:andrew.pennebaker@gmail.com" target="_blank">andrew.pennebaker@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote">
<p dir="ltr">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.</p>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_quote">On Jun 11, 2013 11:05 AM,
"Peter Lemenkov" <<a moz-do-not-send="true"
href="mailto:lemenkov@gmail.com" target="_blank">lemenkov@gmail.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote">
2013/6/11 Andrew Pennebaker <<a
moz-do-not-send="true"
href="mailto:andrew.pennebaker@gmail.com"
target="_blank">andrew.pennebaker@gmail.com</a>>:<br>
> That's nice to know!<br>
><br>
> What about Windows and Mac? For some reason,
rebar isn't in stable Homebrew<br>
> yet, only in head.<br>
<br>
I personally don't care about Windows users since I
don't see any real<br>
reason to use Erlang on Windows. Regarding Mac OS X
- indeed you<br>
should invest your time into enhancing package
system for that<br>
platform.<br>
--<br>
With best regards, Peter Lemenkov.<br>
</blockquote>
</div>
</div>
</div>
<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a moz-do-not-send="true"
href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a moz-do-not-send="true"
href="http://erlang.org/mailman/listinfo/erlang-questions"
target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
erlang-questions mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</blockquote>
<br>
</body>
</html>