Date: Sat, 14 Sep 2013 15:18:59 +0200 From: SpamMePlease PleasePlease <spankthespam@gmail.com> To: freebsd-ports@freebsd.org Subject: How to correctly generate pkg-plist Message-ID: <CAHcXP%2BdCZ2J=h98tFypPPqeH7YSqrN6azvwuLynNi5TntfHzAQ@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHcXP%2BdCZ2J=h98tFypPPqeH7YSqrN6azvwuLynNi5TntfHzAQ>