[erlang-patches] .app and .appup files for erl_interface and jinterface applications (amended)

[alisdair]

I don't see any reason header only applications should not be considered erlang applications and treated as them when possible. As it stands erl_interface and jinterface are the only two things in the lib dir that are not erlang applications and need special treatment but header only projects that do not generate .beam code directly are entirely possible. Of note is the fact that these projects may register processes and have app dependencies of their own necessitating .app/.appup files. Making a distinction between apps in this category and 'erlang applications' just makes tool support more difficult.

Would a solution that loosens the restrictions on what is considered an application so that erl_interface and jinterface qualify (rather than adding admittedly unneeded erlang application requirements to erl_interface and jinterface) receive full tool support be considered?  

--  
alisdair




On Tuesday, 26 March, 2013 at 7:53 AM, Björn-Egil Dahlberg wrote:

> On 2013-03-26 11:45, Anthony Ramine wrote:
> > I would rather correctly create the .app files, not make them optional.
>  
> erl_interface and jinterface shouldn't be considered erlang applications  
> and shouldn't need .app or .appup files.
>  
> They are more build requirements for certain c/java programs or  
> requirements for drivers. Like any other c-dev lib. That is at least my  
> position on the matter.
>  
> In a manifest file I would list them under requirements not dependencies.
>  
> Please consider another solution.
>  
> // Björn-Egil
> _______________________________________________
> erlang-patches mailing list
> erlang-patches@REDACTED (mailto:erlang-patches@REDACTED)
> http://erlang.org/mailman/listinfo/erlang-patches
>  
>  


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-patches/attachments/20130326/56b8d410/attachment.htm>