From owner-freebsd-questions@freebsd.org Thu Jul 6 21:48:04 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F270CD92B25 for ; Thu, 6 Jul 2017 21:48:04 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cdptpa-oedge", Issuer "cdptpa-oedge" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BA4FE80B55 for ; Thu, 6 Jul 2017 21:48:03 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from [65.186.81.207] ([65.186.81.207:51893] helo=raspberrypi.bildanet.com) by cdptpa-omsmta01 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 81/28-10880-C00BE595; Thu, 06 Jul 2017 21:47:57 +0000 Received: from [192.168.1.143] (helo=desktop.example.com) by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1dTEcu-00024o-Li for freebsd-questions@freebsd.org; Thu, 06 Jul 2017 21:47:56 +0000 Subject: Re: FreeBSD did it again (still) To: freebsd-questions@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> <8c1bb853-5eb0-4fae-ee26-5ff4684c2b3a@saunalahti.fi> <1499345128.3276.2.camel@gmail.com> <3cbeca30-8801-d800-edcb-f64ea2f079e0@columbus.rr.com> <9c9b2c25-e65d-3489-e483-d99c2e746e56@FreeBSD.org> From: Baho Utot Message-ID: Date: Thu, 6 Jul 2017 17:47:56 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-RR-Connecting-IP: 107.14.168.6:25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2017 21:48:05 -0000 On 07/06/17 16:57, Stephen Black wrote: > > I'm not familiar with the "synth" program that you're using, but it > appears you are using it to build a local repository, so I guess I > would start there. It looks like a newer project, there is a GIT page > started in January 2016. As I had said, wasn't trying to be an ass, > was just giving my opinion on trying to upgrade source packages on > that big of a leap between versions of FreeBSD. Yes, the base system > should upgrade without issue, but to expect the same from all ports, I > think is asking a lot. I know how to build software as well, and also > have built and used linux from scratch. But that doesn't really mean > anything other than we can both follow written instructions. If I were > to attempt something like this, I would completely wipe out everything > under /usr/local (of course you may want to back up /usr/local/etc) > and reinstall all packages. That way you are ensured there are no old > libraries laying around being linked to accidentally. > Synth is one of the best tools for building ports for FreeBSD. It started on DragonflyBSD and "ported" over to FreeBSD. After John Marino had dust up with the FreeBSD folks the FreeBSD folks kicked him out as a maintainer. I still think that BS and a bad move by FreeBSD folks. IMO he was trying to bring some sanity to FreeBSD build process, something like Arch linux does. Which is/was a good thing. By removing the package repos and rebuild all the ports I use with synth which will create a repository for the ports then doing a pkg upgrade;pkg upgrade;pkg autoremove should get it done. If there is something left over then the port that left old files is incorrect. Synth builds in a clean chroot so it will not link to any old libs. It is impossible, because the old libs do not exist in the chroot that the port was built in. That is the way ports should be built. If FreeBSD ever gets it's act together with base packages, then one could use synth to build base in a clean chroot as well. Again that is how it should be done. I am not holding my breath, IMO base ports will not get finished and be correct in my life time. There is too much to be done and it is going in the wrong direction. Plus IMO the folks running FreeBSD don't listen to others/users too good. I tried base ports and it was a giant cluster I had to use sqlite3 to clean up the pkg database. I forget how many base packages there are, I don't remember but it almost had a package for each shared library. That is nuts. Base should be packaged not unlike LFS, then it would be easy to add remove things to base. Want to use your own binutils then remove the stock one and replace them with your custom one. Want to use Openrc remove the init package and replace with openrc.