From owner-freebsd-current@freebsd.org  Tue Apr 19 15:43:31 2016
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 C6AFAB144B2
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue, 19 Apr 2016 15:43:31 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (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 8687E1DFE;
 Tue, 19 Apr 2016 15:43:31 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1asXoK-000A0f-1O; Tue, 19 Apr 2016 18:43:32 +0300
Date: Tue, 19 Apr 2016 18:43:31 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Alfred Perlstein <alfred@freebsd.org>
Cc: dan_partelly <dan_partelly@rdsor.ro>, freebsd-current@freebsd.org
Subject: Re: [CFT] packaging the base system with pkg(8)
Message-ID: <20160419154331.GH6614@zxy.spb.ru>
References: <571533B8.6090109@freebsd.org> <20160418194010.GX1554@FreeBSD.org>
 <57153E80.4080800@FreeBSD.org> <571551AB.4070203@freebsd.org>
 <5715E1E9.8060507@freebsd.org> <57164068.8080800@freebsd.org>
 <78fb431d2d9b568fd488fae51a1b5f23@rdsor.ro>
 <571643A8.9020702@freebsd.org>
 <d7fb31958a71fbb514ff90ba1ff927be@rdsor.ro>
 <57164C58.8000802@freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <57164C58.8000802@freebsd.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Apr 2016 15:43:31 -0000

On Tue, Apr 19, 2016 at 08:18:48AM -0700, Alfred Perlstein wrote:

> 1) Graciously and rapidly accept steps forward and then contribute to 
> them.  Anything else leaves you stagnant and worse for wear.
> 2) Simple over complex.
> 3) If something someone else did is working for someone, then copy it 
> and move on, don't waste a huge amount of your customer's time trying to 
> make something better until you are sure that just copying it will not 
> suffice.

What is simple -- split base to 10 packages or split base to 800
packages? I think first.
What need for succesufult moved forward after this?
I think ability of spliting and mergering packages at upgrade.
(clang-base => clang-base-c + clang-base-c++, for example.
or clang-base-c + clang-base-c++ => clang-base).

What need for security updates?
I think ability to have file with common name and different content
with multiple installed packages:

base-11.0 contains /usr/sbin/ntpd
 base-11.0-CVE-1234 direct depends to base-11.0 and contains overlaped /usr/sbin/ntpd

As result: few packages, compact security updates, ability to
repackage base.

Optionaly, ability to have packages with "dummy" content, for example
 no-base-ntp-11.0 have record (w/o actual content) about
  /usr/sbin/ntpd with size -791552 (negative size) and checksum of
 actual file, for removing some components.

For this feature give ability to have "skins" packages, installed over
main package.