From owner-freebsd-questions@freebsd.org  Sat Sep 19 13:32:52 2015
Return-Path: <owner-freebsd-questions@freebsd.org>
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 8516C9CEC2F
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Sat, 19 Sep 2015 13:32:52 +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 38F5A1E20
 for <freebsd-questions@freebsd.org>; Sat, 19 Sep 2015 13:32:52 +0000 (UTC)
 (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1ZdIG0-000F59-Tq; Sat, 19 Sep 2015 16:32:48 +0300
Date: Sat, 19 Sep 2015 16:32:48 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Polytropon <freebsd@edvax.de>
Cc: freebsd-questions@freebsd.org
Subject: Re: HTTPS on freebsd.org, git, reproducible builds
Message-ID: <20150919133248.GB21849@zxy.spb.ru>
References: <CAD2Ti2_YNkNi2b=PzFCwu3PVaP8hOzADys3=-k0AqvsDRhJpzA@mail.gmail.com>
 <86vbb7dhaa.fsf@nine.des.no> <20150918134804.GU3158@zxy.spb.ru>
 <86oagzwf8j.fsf@nine.des.no> <20150919125023.GA21849@zxy.spb.ru>
 <20150919151517.739ab70a.freebsd@edvax.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150919151517.739ab70a.freebsd@edvax.de>
User-Agent: Mutt/1.5.23 (2014-03-12)
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-questions@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Sep 2015 13:32:52 -0000

On Sat, Sep 19, 2015 at 03:15:17PM +0200, Polytropon wrote:

> On Sat, 19 Sep 2015 15:50:23 +0300, Slawa Olhovchenkov wrote:
> > On Sat, Sep 19, 2015 at 12:10:36AM +0200, Dag-Erling Smorgrav wrote:
> > 
> > > Slawa Olhovchenkov <slw@zxy.spb.ru> writes:
> > > > freebsd-update builds is inreproducible by the freebsd-update-server bug[s].
> > > 
> > > freebsd-update will most likely be gone in 11.
> > 
> > What is planed for replacement?
> 
> As far as I could understand, pkg will deal with the components
> comprising the OS in the same manner as it does for the ports
> collection. So the kernel, the userland, the sources and so on
> will "become packages" for pkg to install or upgrade. This is
> a similar approach to common package management on Linux, except
> that Linux (as a term to summarize all the many distributions)
> doesn't have an OS ("the base OS") per se.

This is very bad.

> You can already see this kind of development: The documentation
> has become a package, and the package manager itself is a
> package (separated from the OS, which only contains a bootstrap
> loader for the real program). Finally, the installation process
> could become a task of "pkg install", instead of "tar xf". And
> a unification of the infrastructures could lead to additional
> benefits (only _one_ system for both components - OS and ports).

I am have many troubles with this way in Linux.
Kernel and userland versions mismatch.
glibc version incompatible with rpm.
pkunzip.zip problem.
And etc.