From owner-freebsd-pkgbase@freebsd.org Thu Jan 28 17:45:20 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 E1288A7131C; Thu, 28 Jan 2016 17:45:19 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B24C81D45; Thu, 28 Jan 2016 17:45:19 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pa0-x234.google.com with SMTP id ho8so26449572pac.2; Thu, 28 Jan 2016 09:45:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=RtTFKHM58c3Th5W+5608AsI6zB/rj6YKo3m8/KIUbfA=; b=IUsjzwQiuxA2XlF91X0SBOv9A5gdb7KS+PoddgAiWNMMe2J7+Rh+vXDPYJla5vCleq 2wlmcATetUROtMq7RM7FfAQcvStC3adRjYgXOVI4jm7JS9hO8gPqLT43du6DiSPrygo8 IKBE3e5/mjENc/s8du58DAKBXeeTLhAR0L4DR3KH8zEd4joroE1vLF0LAnXO32xMp64U 4UKLcCLhepUHgMMuqKsSiPq3x9clgUYI35lf1b5Q4Z100v8INk/UDmKZRltzhv3XvBPW U8MQ3VymVAhgFI9Eb9IaDZedQj9RwzKq6Rw/NlMb1Lv/iDRAafOYHDeffOvIUwpz0k+K sAOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=RtTFKHM58c3Th5W+5608AsI6zB/rj6YKo3m8/KIUbfA=; b=VzkrnWdZD51tukfnM51yn9hXf+1vA2fwdbnFKLtyKgjJF5p5niZPoYlWdRlMhcpjD5 hsgOLPRJSkF1pu7LWC2AgThIKYhrwEfdiCth9uuZNZp8kz3LWpPjzzuESK3e2bGWEpO9 on6BcrgpkqlTaB7Wfka9TXK9wuC/iWkWU2/xApwhevRZDJvgxjZiTnpGRj/mNC0rlaBC 7QtN76WBANJn2y+6LfPqopcDctcsT56QkImNJ66m7UAEISp/vke1xo33+f8EjB5IgFHe jzntKrwsnWMxzwZ+qrtZMX5L8x7ysCdE4UCr37Cpvh4rRxPGJ0DKpqF2SKIFph2XkQ6A 3VWQ== X-Gm-Message-State: AG10YOTy1uYo7JAdMR8IWTYpqAx9fc1qZUzEMdj65cdbeD7ezOxWdKfTMAD3NcK7Jb8hPQ== X-Received: by 10.67.24.104 with SMTP id ih8mr6392707pad.124.1454003119350; Thu, 28 Jan 2016 09:45:19 -0800 (PST) Received: from [22.160.77.234] ([172.56.38.103]) by smtp.gmail.com with ESMTPSA id 70sm17832950pfc.69.2016.01.28.09.45.17 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 28 Jan 2016 09:45:18 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Packaging the FreeBSD base system with pkg(8) From: NGie Cooper X-Mailer: iPhone Mail (13D15) In-Reply-To: <20160128173836.GD88527@zxy.spb.ru> Date: Thu, 28 Jan 2016 09:45:16 -0800 Cc: Baptiste Daroussin , Thomas Mueller , freebsd-current@freebsd.org, freebsd-pkgbase@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <3A5AAF2B-F9CF-41B3-A97C-FF208803428A@gmail.com> 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> To: Slawa Olhovchenkov 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 17:45:20 -0000 > On Jan 28, 2016, at 09:38, Slawa Olhovchenkov wrote: >=20 >> On Thu, Jan 28, 2016 at 09:28:32AM -0800, NGie Cooper wrote: >>=20 >>=20 >>> On Jan 28, 2016, at 08:06, Slawa Olhovchenkov wrote: >>=20 >>=20 >> ... >>=20 >>> 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. >>=20 >> 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). >=20 > 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. >=20 >> 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. >=20 > 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 i= s going to be more entertaining across interface breaks; it might be that pk= gng is at the point where it's stable enough that interfaces won't change (u= nlikely, software tends to be fluid), or backwards compatibility will need t= o be maintained for older versions of pkgng. Also, consider that you're going to be allowing upgrades from older RELEASE v= ersions of the OS which might be using a fixed copy of pkgng -- how are you g= oing to support that? Thanks! -NGIE=