From owner-svn-ports-all@FreeBSD.ORG  Sat Aug 23 12:39:48 2014
Return-Path: <owner-svn-ports-all@FreeBSD.ORG>
Delivered-To: svn-ports-all@freebsd.org
Received: from mandree.no-ip.org (freefall.freebsd.org
 [IPv6:2001:1900:2254:206c::16:87])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 582F5EE5;
 Sat, 23 Aug 2014 12:39:48 +0000 (UTC)
Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1])
 by apollo.emma.line.org (Postfix) with ESMTP id 3BB8D23CEB4;
 Sat, 23 Aug 2014 09:46:46 +0200 (CEST)
Message-ID: <53F846E6.6000307@FreeBSD.org>
Date: Sat, 23 Aug 2014 09:46:46 +0200
From: Matthias Andree <mandree@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: koobs@FreeBSD.org, Bryan Drewery <bdrewery@FreeBSD.org>, 
 ports-committers@freebsd.org, svn-ports-all@freebsd.org, 
 svn-ports-head@freebsd.org
Subject: Re: svn commit: r365566 - head/Tools/scripts
References: <201408211556.s7LFuE0p041046@svn.freebsd.org>
 <53F61E42.4050104@FreeBSD.org> <53F6267E.9020909@FreeBSD.org>
 <53F62802.3030006@FreeBSD.org> <53F62AB5.6060802@FreeBSD.org>
In-Reply-To: <53F62AB5.6060802@FreeBSD.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-BeenThere: svn-ports-all@freebsd.org
X-Mailman-Version: 2.1.18-1
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: Sat, 23 Aug 2014 12:39:48 -0000

Am 21.08.2014 um 19:21 schrieb Kubilay Kocak:

> We probably could have used one of these in python@ for cleaning up
> setuptools (old) and distribute remnants that caused many issues for
> users as we chased upstream, even with good instructions in UPDATING
> (since we couldnt cover all cases)
> 
> I wonder too, to what extent a relatively generic interface for these
> things might be possible.

I wonder if an "annotated list" of versions would help the pkg solver
handle these; if the metadata for a new package lists "Obsoletes:
blah<3.0" then the solver would automatically remove blah<3.0.

I haven't investigated how far the automatic solving in pkg works for
such situations especially if you have the version part of the package
name as in py27-* and py34-*, or db48 vs. db6.

Basically it is a question if there are alternative versions to choose
from on one hand, or on the other hand there is a clear (to the tool,
anyways) upgrade path for a package that has gone away, like db43 to db5.