How to correctly generate pkg-plist

[SpamMePlease PleasePlease]

Hi,

I was wondering if there's anyone who could give me some advice on it? This
is an issue that stops me from sending otherwise fully working port.

Regards,
S.


On Sat, Sep 14, 2013 at 2:18 PM, SpamMePlease PleasePlease <
spankthespam at gmail.com> wrote:

> Hi,
>
> I am writing new port that compiles and installs huge number of Erlang
> libraries. Everythig is working fine until there's a need of deinstallation
> or to make package - the problem is that the user might have older Erlang
> version (for example, coming from ports unpacked during installation from a
> cd) and when compiled with such Erlang, everything will be working, except
> for the fact that older Erland will compile different versions of
> libraries, and therefore my 2000 lines long pkg-plist will no longer be
> valid. I thought I can remedy that simply by not listing the lib names and
> their dir paths to avoid such situation, but to use @unexec ${RM} -rf
> lib/portname, but then there's a problem with make package, that is not
> containing all required and compiled libs.
>
> How to solve that situation?
>
> Regards,
> S.
>