Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Jul 2017 12:52:34 -0400 (EDT)
From:      doug <doug@fledge.watson.org>
To:        Matthew Seaman <matthew@FreeBSD.org>
Subject:   Re: FreeBSD did it again (still)
Message-ID:  <alpine.BSF.2.20.1707111220280.40153@fledge.watson.org>
Resent-Message-ID: <alpine.BSF.2.20.1707111948420.40153@fledge.watson.org>
In-Reply-To: <9c9b2c25-e65d-3489-e483-d99c2e746e56@FreeBSD.org>
References:  <27b3c757-1f00-a033-03f6-303a82ab65f2@columbus.rr.com> <3ce31ee2-5e35-d31c-71ca-dc95ece2dd61@intersonic.se> <020431a6-1a7d-d80e-0725-585c21f3ef27@columbus.rr.com> <563b14d5-ebfb-62b6-28ac-3ebbd663d067@intersonic.se> <e2cab146-89c9-23b0-e6ac-6222d8747277@columbus.rr.com> <8c1bb853-5eb0-4fae-ee26-5ff4684c2b3a@saunalahti.fi> <1499345128.3276.2.camel@gmail.com> <3cbeca30-8801-d800-edcb-f64ea2f079e0@columbus.rr.com> <alpine.BSF.2.21.1707060743420.80012@wonkity.com> <9c9b2c25-e65d-3489-e483-d99c2e746e56@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 6 Jul 2017, Matthew Seaman wrote:

> On 2017/07/06 14:46, Warren Block wrote:
>> On Thu, 6 Jul 2017, Baho Utot wrote:
>>
>>> Well FYI the upgrade base 10.1 to 11.0-p10 when as expected. Update
>>> the ports to the current quarterly was a tragic happening.  I have
>>> done this before upgrade a desktop from 10.3 to 11.0-p0 then to
>>> 11.0-p9.  Again the ports just did not work as it resulted in a broken
>>> desktop each time.  I started using the quarterly ports branch
>>> thinking I get some stablilty.  No stability to be found.  Should I
>>> user be able to update without going thru a weeks worth of debugging?
>>> I think that is not too much to ask.
>>
>> It might or might not be obvious, but after going from FreeBSD 10 to 11
>> all ports must be reinstalled.  It is not possible to upgrade only some
>> ports without mysterious breakages.
>
> pkg(8) is actually smart enough to realise that the ABI-version of the
> installed packages doesn't match either the ABI-version of the running
> kernel[*] or the ABI-version of the repository and it /should/ attempt
> to update or reinstall all installed packages to fix that.
>
> Much of the time that will "just work" -- but not always, which is why
> the standard advice is still to delete and reinstall all packages on a
> major version upgrade.  Working out when and why pkg(8) can fail to do
> this correctly and teaching it how to get it right would be a really
> useful contribution.
>
One thing I did not see highlighted in this thread was, it's a laptop. As this 
is the world I live in, I feel the need to say things ain't that bad. Things 
would be much better if more Xorg and www ports developers ran FreeBSD 
workstations. There is a reason that few companies pay anyone to port the wifi 
and graphics drivers to FreeBSD. I am told many of these were likely developed 
on FreeBSD because of superior debugging tools. In the current world things are 
pretty good to great, if you do the following: don't live on the FreeBSD edge 
unless you are willing to and can help find bugs; make sure your graphics card 
is supported before buying (for me wifi would be a plus); and lastly, if you do 
not want to occasionally have to do some serious back-tracking install Xorg, 
Mozilla stuff and your windowing preference (xfce for me) on a 'clean' system.
In that order.

So on 10.3, soon to be 10.4 life is good to great. pkg is a monumental 
improvement and if you are not gaming a $700 laptop will outperform a lot more 
expensive stuff running Mac or Windows. Will a small hicup with firefox I added 
libreoff and gimp to a working system. I did test this path on a laptop that I 
hosed trying to upgrade something in xfce. My experiences; YMMV :)






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