From owner-svn-ports-all@FreeBSD.ORG  Wed Jul 16 13:46:34 2014
Return-Path: <owner-svn-ports-all@FreeBSD.ORG>
Delivered-To: svn-ports-all@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 1033)
 id 48A5CF04; Wed, 16 Jul 2014 13:46:34 +0000 (UTC)
Date: Wed, 16 Jul 2014 13:46:34 +0000
From: Alexey Dokuchaev <danfe@FreeBSD.org>
To: Vsevolod Stakhov <vsevolod@FreeBSD.org>
Subject: Re: svn commit: r361646 - in head/net/samba36: . files
Message-ID: <20140716134634.GA53978@FreeBSD.org>
References: <201407122229.s6CMTN42057554@svn.freebsd.org>
 <CALdFvJGQq=PNpAqBBEZXi-q0GT=Ro-fRSjGcHFR1R01=FBtQOQ@mail.gmail.com>
 <53C322A7.2090705@marino.st> <20140714003112.GA54756@mouf.net>
 <CALdFvJEvf4-RSJNUVxX08T8K-tq9PoKge-XxmhDafAn_QxjEcg@mail.gmail.com>
 <53C451FA.2020304@marino.st> <20140715170501.GA73101@FreeBSD.org>
 <53C5618F.2020104@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <53C5618F.2020104@FreeBSD.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: svn-ports-head <svn-ports-head@freebsd.org>,
 Benjamin Kaduk <bjk@FreeBSD.org>, svn-ports-all <svn-ports-all@freebsd.org>,
 "ports-committers@freebsd.org" <ports-committers@freebsd.org>
X-BeenThere: svn-ports-all@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: SVN commit messages for the ports tree <svn-ports-all.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-ports-all>,
 <mailto:svn-ports-all-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/svn-ports-all/>
List-Post: <mailto:svn-ports-all@freebsd.org>
List-Help: <mailto:svn-ports-all-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-ports-all>,
 <mailto:svn-ports-all-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jul 2014 13:46:34 -0000

[ CC list trimmed; bjk@ added (see below) ]

On Tue, Jul 15, 2014 at 06:14:55PM +0100, Vsevolod Stakhov wrote:
> Let me explain the situation with pkg. Pkg needs to find so called
> ``upgrade chains'' that are used to upgrade packages. To find out
> packages that are suitable for upgrade we use origins in pkg 1.2 and
> name~origin in pkg 1.3.
> 
> However, each package is identified by a special field called
> `manifestdigest'. In pkg 1.2, this field is just sha256(manifest).
> Unfortunately, this means that if *any* field of a package is changed a
> version bump is required. By fields I mean files and directories as well
> which leads thus to a policy where we need to bump a revision even if we
> have meaningless changes in the files a package provides (that happens
> after this particular change).
> 
> With pkg 1.3 this behaviour has been changed to recognize the following
> fields only:
> 
> *  name
> *  origin
> *  version
> *  arch
> *  maintainer
> *  www
> *  message
> *  comment
> *  options
> 
> Hence, I think that with the release 1.3 of pkg we should define
> revision bump policy to reflect this change.

I've recalled that bjk@ mentioned once that he was giving a talk about some
interesting features of Debian packaging at the ports devsummit at BSDCan.
Maybe we can learn a thing or two from those guys?  Ben, can you share your
opinion on Vsevolod's proposal (you might want to see other messages in the
thread first)?  Thanks.

./danfe