Date: Thu, 16 Jan 2014 00:52:22 +0000 From: "Montgomery-Smith, Stephen" <stephen@missouri.edu> To: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: Re: Qpopper Port Message-ID: <52D72D43.6010006@missouri.edu> In-Reply-To: <234AA4B5-BAEB-4067-99FC-5AA803033B6C@lafn.org> References: <234AA4B5-BAEB-4067-99FC-5AA803033B6C@lafn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/15/2014 06:08 PM, Doug Hardie wrote: > I am going to have to give up maintaining qpopper. Not because I don't h= ave the interest or time, but because I simply cannot update any port. The= old port system may have had issues, but it worked!!! The new one does no= t. I am completely unable to upgrade or install any ports on a 9.1 or high= er system. I have a number of those in production and will have to now res= ort to obtaining ports from the original sources and making them work on my= systems. Its a colossal pain in the *&^*&^. Call me old fashioned. But I am still using FreeBSD-8 with the old ports system. I also never got into the idea of using portmaster or any of those fancy tools, and still use pkg_version and pkg_delete and "cd /usr/ports/xxx/yyy && make install clean" to maintain my ports. I did install FreeBSD-10 on one computer recently, but I am experiencing the same problems with the ports I am maintaining - I cannot build many of them because dependent ports are breaking. Also, I get periodic emails from pkg-fallout@FreeBSD.org explaining how one or other of my ports don't build properly. Some of the error messages are clearly problems with switching from gcc to clang, and are easily fixed. But some of the other problems seem to be problems with FreeBSD-10 itself (especially /usr/bin/ld), or problems with pkgng. I do hope EOL for FreeBSD-8 is still some length of time away. If I had to upgrade today, it would create difficulties for me.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52D72D43.6010006>