<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 07/18/2014 08:38 AM, Andreas
Schumacher wrote:<br>
</div>
<blockquote
cite="mid:CAA6B5+7ZnwZBA4bjrgGapp65ufW9y5CU6r=4FqDd7y84nUOVBA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Hi Tristan,</div>
<div><br>
</div>
<div>As Kenneth responded to your post [1] a couple of months
ago, there is room for improvement wrt to the handling of
runtime_dependencies. We will continue to work on that issue,
and we may write an EEP for collecting community input;
although, I won't promise the latter. In any case, we
appreciate your input and will consider it, regardless of an
EEP.</div>
<div><br>
</div>
<div>[1]: <a moz-do-not-send="true"
href="http://erlang.org/pipermail/erlang-questions/2014-April/078730.html">http://erlang.org/pipermail/erlang-questions/2014-April/078730.html</a> </div>
<div><br>
</div>
<div>
<div>Andreas</div>
<div>
<br>
</div>
<div>---</div>
<div><br>
</div>
<div>Andreas Schumacher, Erlang/OTP, Ericsson AB</div>
</div>
<div><br>
</div>
<br>
<div class="gmail_quote">
On 17/07/14 23:35, "Tristan Sloughter" <<a
moz-do-not-send="true" href="mailto:t@crashfast.com">t@crashfast.com</a>>
wrote:<br>
<br>
>I wrote the list about runtime_dependencies in .app files
now in 17+ a<br>
>couple months ago, <a moz-do-not-send="true"
href="http://www.erlang.org/doc/man/app.html"
target="_blank">http://www.erlang.org/doc/man/app.html</a><br>
><br>
>Today I was informed that if you were to take all the<br>
>runtime_dependencies defined for kernel-3.x and their<br>
>runtime_dependencies you'd end up having wx as one, even
for OTP built<br>
>without wx support.<br>
><br>
>Yes, I know the second warning on the app man page says
that just<br>
>because it is in there today doesn't mean it will be in
the future and<br>
>is actively being worked on.<br>
><br>
>My question is, wouldn't it be nice if the OTP team made
an EEP that the<br>
>community could comment on for this? :)<br>
><br>
>Tristan<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>
</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>
<tt>One suggestion is that it would be nice to not have to parse a
string to get the version or the constraint from the entry. So,
keeping the application name as an atom and the version as a
string, the relational operator could be done as an atom:<br>
<a class="moz-txt-link-freetext" href="http://www.erlang.org/doc/man/app.html">http://www.erlang.org/doc/man/app.html</a> example of "kernel-3.0"
becomes {kernel, '>=', "3.0"}<br>
If the normal relational operators are handled like atoms, it
seems like this would become explicit and easier to use (no extra
parsing required). This is similar to what was in the older email
thread, but keeps the version separate from the relational operator.<br>
<br>
It would be nice to clarify whether it is an error for
'runtime_dependencies' to provide a constraint for an application
that is not a dependency listed in either 'included_applications'
or 'applications'. It seems like it should be limited to
providing constraints on its dependencies (when considering the
whole tree of dependencies for that particular application), since
otherwise it could impact unrelated applications with invalid
constraints.<br>
</tt>
</body>
</html>