2013/9/14 SpamMePlease PleasePlease <spankthes...@gmail.com>:
> 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?General idea for complex plist handeling is to use a dynamic plist. I think java/eclipse is a good example. See also http://www.freebsd.org/doc/en/books/porters-handbook/plist-dynamic.html for further discussion on static vs dynamic plist. Joris > > Regards, > S. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
