Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Sep 2013 08:00:30 +0200
From:      joris dedieu <joris.dedieu@gmail.com>
To:        SpamMePlease PleasePlease <spankthespam@gmail.com>
Cc:        freebsd-ports <freebsd-ports@freebsd.org>
Subject:   Re: How to correctly generate pkg-plist
Message-ID:  <CAPd55qDGxtjgyc=%2B5pdLfeXh8%2BpQH1JD77GfUdzDwhPwmK9dtw@mail.gmail.com>
In-Reply-To: <CAHcXP%2BdCZ2J=h98tFypPPqeH7YSqrN6azvwuLynNi5TntfHzAQ@mail.gmail.com>
References:  <CAHcXP%2BdCZ2J=h98tFypPPqeH7YSqrN6azvwuLynNi5TntfHzAQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
2013/9/14 SpamMePlease PleasePlease <spankthespam@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-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPd55qDGxtjgyc=%2B5pdLfeXh8%2BpQH1JD77GfUdzDwhPwmK9dtw>