On Fri, Jun 01, 2012 at 08:32:08PM +0100, Chris Rees wrote: > On 1 June 2012 16:20, Nomen Nescio <nob...@dizum.com> wrote: > >> Dear All , > >> > >> There is a thread > >> > >> "Why Are You Using FreeBSD ?" > >> > >> > >> I think another thread with the specified subject '"Why Are You NOT Using > >> FreeBSD ?" may be useful : > >> > >> > >> If you are NOT using FreeBSD for any area or some areas , would you please > >> list those areas with most important first to least important last ? > > > > 1. The X-org changeover a few years ago screwed up a FreeBSD installation I > > had been using so badly I never trusted FreeBSD's rolling update ports > > system again. That should have been a major FreeBSD release, but instead it > > was done just in the ports with no version bump and no choice and no notice > > unless you read the fine print. > > > > 2. Broken ports galore. Much of the stuff I wanted broke on AMD64 after > > downloading tarballs for hours. Not good. Contacted package maintainer and > > received answer: yeah, I know it doesn't work on AMD64. > > That is unacceptable. Submit a PR next time you find something like > that-- ports that are broken on an arch should be marked as such so > people don't waste their time as you have been made to.
I guess he made his experiences with that some years ago when support for amd64 in the ports was not very mature. But this has changed since then, apart from a few ports almost all of them should work on amd64 without problems.
pgpvcEUjUowyr.pgp
Description: PGP signature
