Hi, This mail is to highlight current status of my find-requires-provides-for-erlang story. I've experimented at home:matwey:erlang and I've used new rpm fileattrs interface to run modified Lemekov's scripts. The first issue is that I had to broke erlang-wx (see http://lists.opensuse.org/opensuse-packaging/2013-03/msg00079.html ) The second is more sophisticated. As you know, you can compile in a link to any module and any function (ever not existing at all). Until the code want to call this function, you never know that. This opportunity is used quite often. Let us take a look at erlang-rfc4672. It has interfaces to different http servers: cowboy, mochiweb, inets. The scripts are able to extract all symbols after package built, but... We don't have at all packages for cowboy and mochi, no package provides the modules required by erlang-rfc4672. So, some packages built with auto-requires are not installable. (and formally they are inconsistent, they may potentially have bugs) And I don't know how to gracefully track this. In C, you need library to be installed at compile-time in order to link your exe with it. In Erlang, you do not. Maybe we need some lint-checker to reject package if we found that it requires module not installed at our build-host. More interesting that even from this code: Mod = list_to_atom("demo"), %% Fool xref tests case file:set_cwd(Demo) of ok -> apply(Mod, start, []), I was able to extract erlang:mod(demo) with R15/16. :) -- With best regards, Matwey V. Kornilov http://0x2207.blogspot.com xmpp:0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org