Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 1 Jun 2012 20:32:08 +0100
From:      Chris Rees <crees@FreeBSD.org>
To:        Nomen Nescio <nobody@dizum.com>, stable@freebsd.org
Subject:   Re: Why Are You NOT Using FreeBSD ?
Message-ID:  <CADLo838vpbVP3caXG7LF7st4inWnMLi5zB3U1hD2dkXwf8ZLBg@mail.gmail.com>
In-Reply-To: <2730bd1bab4223e718193254cb8bbd60@dizum.com>
References:  <CAOgwaMvsv3e1TxDauV038Pp7LRiYeH7oAODE%2Bw-pxHt9oGrXMA@mail.gmail.com> <2730bd1bab4223e718193254cb8bbd60@dizum.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 1 June 2012 16:20, Nomen Nescio <nobody@dizum.com> wrote:
>> Dear All ,
>>
>> There is a thread
>>
>> "Why Are You Using FreeBSD ?"
>>
>>
>> I think another thread with the specified subject =A0 '"Why Are You NOT =
Using
>> FreeBSD ?" may be useful :
>>
>>
>> If you are NOT using FreeBSD for any area or some areas , would you plea=
se
>> 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 noti=
ce
> 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 an=
d
> 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.

Chris



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo838vpbVP3caXG7LF7st4inWnMLi5zB3U1hD2dkXwf8ZLBg>