From owner-freebsd-pkgbase@freebsd.org Thu Jan 28 18:25:08 2016 Return-Path: Delivered-To: freebsd-pkgbase@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 2B5FDA700BA for ; Thu, 28 Jan 2016 18:25:08 +0000 (UTC) (envelope-from jmaloney@pcbsd.org) Received: from barracuda.ixsystems.com (mail.ixsystems.com [69.198.165.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.ixsystems.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 121A51331 for ; Thu, 28 Jan 2016 18:25:07 +0000 (UTC) (envelope-from jmaloney@pcbsd.org) X-ASG-Debug-ID: 1454005505-08ca04766a02ff0002-wjM0Vu Received: from [10.0.1.13] (ip72-209-162-1.ks.ks.cox.net [72.209.162.1]) by barracuda.ixsystems.com with ESMTP id 8a3QJXiZxfl7SHhZ (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 28 Jan 2016 10:25:06 -0800 (PST) X-Barracuda-Envelope-From: jmaloney@pcbsd.org X-Barracuda-AUTH-User: jmaloney@pcbsd.org X-Barracuda-Apparent-Source-IP: 72.209.162.1 Subject: Re: Packaging the FreeBSD base system with pkg(8) To: freebsd-pkgbase@freebsd.org X-ASG-Orig-Subj: Re: Packaging the FreeBSD base system with pkg(8) References: <20160127223323.GG98557@FreeBSD.org> <183431.62409.bm@smtp111.sbc.mail.ne1.yahoo.com> <20160128131806.GB67200@ivaldir.etoilebsd.net> <20160128160622.GB88527@zxy.spb.ru> <20160128173836.GD88527@zxy.spb.ru> <3A5AAF2B-F9CF-41B3-A97C-FF208803428A@gmail.com> <20160128181253.GE88527@zxy.spb.ru> From: Joe Maloney Message-ID: <56AA5D52.8040203@pcbsd.org> Date: Thu, 28 Jan 2016 12:26:26 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <20160128181253.GE88527@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Barracuda-Connect: ip72-209-162-1.ks.ks.cox.net[72.209.162.1] X-Barracuda-Start-Time: 1454005505 X-Barracuda-Encrypted: ECDHE-RSA-AES128-GCM-SHA256 X-Barracuda-URL: https://10.2.0.41:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at ixsystems.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=8.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.26539 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-BeenThere: freebsd-pkgbase@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Packaging the FreeBSD base system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2016 18:25:08 -0000 I have been planning for some months to integrate this technology into what will be the future offering of something I have been working on. :) http://skynet.desktopbsd.net/packages/ Thus far I had only been able to build the world for those curious what the layout looks like an older version can be shown at the site above. I've been digging into the code, and I had noticed the stagekernel was missing which is why the kernel was not built in that repo. However now I see that gjb has committed that. So I will begin re-attempting builds, and storing them at the above location. I am curious. How will updates to or even the installation of items into /etc be handled? Will there be a special tool for that? After 11-RELEASE will there soon be a binary updating 11-STABLE, or 12-CURRENT when this is all said, and done? I am excited for this! Joe Maloney On 01/28/16 12:12, Slawa Olhovchenkov wrote: > On Thu, Jan 28, 2016 at 09:45:16AM -0800, NGie Cooper wrote: > >>> On Jan 28, 2016, at 09:38, Slawa Olhovchenkov wrote: >>> >>>> On Thu, Jan 28, 2016 at 09:28:32AM -0800, NGie Cooper wrote: >>>> >>>> >>>>> On Jan 28, 2016, at 08:06, Slawa Olhovchenkov wrote: >>>> >>>> ... >>>> >>>>> What about upgrade strongly outdated system? >>>>> For example 11.0 at time 18.0? I.e. packages for 11.0 don't available, >>>>> pkg from 11.0 don't undertund package base from 18.0 and etc. >>>> This is an important question to ask and solve. There might be >>>> points in time where seamless upgrades are not possible, and instead >>>> you need to hop from release to release (this is not ideal, but it >>>> could happen). >>> I see two side of this problem: support in sofware and support in >>> infrastructure (ftp.freebsd.org and etc.). Because pkg is not part of >>> base FreeBSD and live in ports -- this hops need to preserve (and >>> testing?) packages collections for all past releases and don't move it >>> to archive. And regular resigning package databases. And I miss >>> somewere. >>> >>>> For instance, at $work we're allowing upgrades from version X to Y, >>>> and Y to Z, but not direct upgrades from X to Z. Part of the >>>> rationale behind this change is, deprecation of platforms and the >>>> change in upgrade framework, which requires upgrading from blessed >>>> releases proven to work with the new framework. >>> This is common practic, yes. >>> This is acceptably if possible got all necessary in time 18.0 for >>> upgrade from 11.0. >> Yes. Given the hiccups going from pkg 1.4 to 1.6 with the plist >> stuff, this is going to be more entertaining across interface >> breaks; it might be that pkgng is at the point where it's stable >> enough that interfaces won't change (unlikely, software tends to be >> fluid), or backwards compatibility will need to be maintained for >> older versions of pkgng. > >> Also, consider that you're going to be allowing upgrades from older >> RELEASE versions of the OS which might be using a fixed copy of >> pkgng -- how are you going to support that? > I see two hudge problem for support upgrades from older RELEASE > versions (supported too): key (used for repo signing) change and need > to access ports packages to install (installed outdated release can't > find pkg packet for install). > > Can you more detailed describe current propolsal of new packaging > system? pkg is part of base installed packages? Or after installing > base packages pkg installed from `ports`? For disc1.iso case. > > How handled boot/device.hints and var/db/etcupdate? > > How handled boot block updates? > _______________________________________________ > freebsd-pkgbase@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-pkgbase > To unsubscribe, send any mail to "freebsd-pkgbase-unsubscribe@freebsd.org"