Date: Sat, 01 Feb 2014 08:45:44 +0100 From: Guido Falsi <mad@madpilot.net> To: nano <nanotek@bsdbox.co>, freebsd-ports@freebsd.org Subject: Re: libiconv on 10.0-RELEASE Message-ID: <52ECA628.9080801@madpilot.net> In-Reply-To: <52ECA567.7010109@FreeBSD.org> References: <52EC99E0.2080801@bsdbox.co> <52EC9C3D.6060505@FreeBSD.org> <52EC9ED4.6030604@bsdbox.co> <52ECA1ED.5030205@FreeBSD.org> <52ECA410.3050606@bsdbox.co> <52ECA567.7010109@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/01/14 08:42, Guido Falsi wrote: > On 02/01/14 08:36, nano wrote: > >>>> I appreciate your advice, but I think I will wait before updating these >>>> ports. Hopefully things get cleaned up a bit. I would not be happy if >>>> something breaks. >>> >>> I understand. I still have not had a good look at r341775 and have only >>> built ports affected by it in poudrirere, and using them as binary >>> packages, which works fine. >>> >> >> I may create a jail to somewhat emulate my live environment and conduct >> a test run to see if any problems arise. > > As a personal suggestion, if you have the expertise to do that, you > should investigate using poudriere to build your own binary packages > repository and upgrade your live, production systems from there. Forgot to mention, if you're not using any non standard option in your systems and using only RELEASES, then you could directly use the packages from the official repositories. -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52ECA628.9080801>