From owner-freebsd-pkgbase@freebsd.org Tue Apr 30 06:32:40 2019 Return-Path: Delivered-To: freebsd-pkgbase@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B238D158519B for ; Tue, 30 Apr 2019 06:32:40 +0000 (UTC) (envelope-from franco@opnsense.org) Received: from mail.opnsense.org (mail.opnsense.org [IPv6:2001:1af8:4700:a129:100::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CBAAB8ECB3 for ; Tue, 30 Apr 2019 06:32:39 +0000 (UTC) (envelope-from franco@opnsense.org) Received: from localhost (mail.opnsense.org [127.0.0.1]) by mail.opnsense.org (Postfix) with ESMTP id 90F8E14EC61; Tue, 30 Apr 2019 08:32:30 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail.opnsense.org Received: from mail.opnsense.org ([127.0.0.1]) by localhost (mail.opnsense.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O94og1jqvLf6; Tue, 30 Apr 2019 08:32:30 +0200 (CEST) Content-Type: text/plain; charset=us-ascii DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=opnsense.org; s=dkim; t=1556605950; bh=SnPtqVtaFqzzzOuCZL4IZsrPVs8LYkGwKu/dSXPF2kg=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=LEZDmZSrH2DXsMRNe4eA+a6dnbOzl4IOAFRNjmAiKL9ObpJ0tr1k3BvYvt3ivGF5t lHetEfg+1X7s0MzQLF7cqEq1KH+RJRGswjKPiN2xOmPo63VXAWOHxAQO6fBvKNxRdz /8YTovMBkO9EzpP4REO1y+zaRnevxxoBt9/I0L2Q= Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) Subject: Re: CFT: FreeBSD Package Base From: Franco Fichtner In-Reply-To: <8B10CAFD-88A1-4DAD-92C2-93F5DE4B3402@cschubert.com> Date: Tue, 30 Apr 2019 08:32:29 +0200 Cc: freebsd-pkgbase@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <7B9F9F37-9DCB-4B9D-BEF1-8C3092331DD0@opnsense.org> References: <201904291441.x3TEfMid072751@gndrsh.dnsmgr.net> <201904291931.x3TJV73d079802@slippy.cwsent.com> <23751.25464.908633.101215@khavrinen.csail.mit.edu> <8B10CAFD-88A1-4DAD-92C2-93F5DE4B3402@cschubert.com> To: Cy Schubert X-BeenThere: freebsd-pkgbase@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Packaging the FreeBSD base system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2019 06:32:40 -0000 > On 30. Apr 2019, at 2:25 AM, Cy Schubert = wrote: >=20 > As for updating, freebsd-update is mostly there to accomplish your = requirement without pkgbase. Which begs the question, if we're simply = replacing freebsd-update and it does most of what we want why the extra = effort? Unless we want to solve more than just this problem? Which BTW I = think we do. There's hbsd-update, pfSense-upgrade and opnsense-update precisely because pkgbase was pulled ever since it's first ETA in 11.0 and the subsequent non-delivery. freebsd-update is not the answer. Speaking for opnsense-update[1] specifically it's a shell script with a bit of bloat for handling package updates as normal and otherwise use base.txz and kernel.txz and arbitrary signatures in pkg (built upon the idea of pkg.txz.sig) to verify their signature directly linked to the fingerprints of the pkg repo used -- all well under 1000 LOC counting whitespaces for readability and battle- proven since 2015. My point is simply this: The sole focus on "the" pkgbase that will solve all issues and the unwillingness to cooperate on "pkgbase" at the same time has made the situation much much worse than it should have been for FreeBSD users and blocked the road for other types of improvements in the update area for a number of years now. It's time to step up instead of further dividing the topic so I want to thank Kris for his effort very much. Cheers, Franco [1] = https://raw.githubusercontent.com/opnsense/update/master/update/opnsense-u= pdate.sh=