From owner-freebsd-ports@FreeBSD.ORG  Thu Feb  6 19:50:12 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 70F32980
 for <freebsd-ports@freebsd.org>; Thu,  6 Feb 2014 19:50:12 +0000 (UTC)
Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 436E21D75
 for <freebsd-ports@freebsd.org>; Thu,  6 Feb 2014 19:50:11 +0000 (UTC)
Received: from [192.168.0.22] (unknown [130.255.19.191])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by shepard.synsport.net (Postfix) with ESMTP id E25D2438BE;
 Thu,  6 Feb 2014 13:49:53 -0600 (CST)
Message-ID: <52F3E751.50401@marino.st>
Date: Thu, 06 Feb 2014 20:49:37 +0100
From: John Marino <freebsd.contact@marino.st>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Randy Pratt <bsd-unix@embarqmail.com>
Subject: Re: [FreeBSD-Ports-Announce] Time to bid farewell to the old pkg_
 tools
References: <201402052202.s15M2Lha059200@fire.js.berklix.net>
 <52F2C0C8.5010203@gmx.de>
 <CAN6yY1uyXNp_c4PruKM89S9g0Y0QAs02cu5Z-dx3oSg1yZC19Q@mail.gmail.com>
 <52F32F7C.2030601@infracaninophile.co.uk>
 <CAN6yY1smkF2SdV190fE1KWKtr9FCiXBZ-08bQ=kc8vpDSnwooQ@mail.gmail.com>
 <20140206111330.8df9c79e0ec1b9d2ffc9d0a1@embarqmail.com>
In-Reply-To: <20140206111330.8df9c79e0ec1b9d2ffc9d0a1@embarqmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Kevin Oberman <rkoberman@gmail.com>,
 FreeBSD Ports ML <freebsd-ports@freebsd.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: marino@freebsd.org
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2014 19:50:12 -0000

On 2/6/2014 17:13, Randy Pratt wrote:
> My experience with mixing ports and packages dates back to 2.2.5 and
> the disasters it created.  Most of the problems were created by the
> ports tree and package builds not being syncronized.  I switched to
> ports exclusively and have not had those problems again.  If a
> mechanism existed to svn update a ports tree to the revision level of
> the package build I would probably try to use packages for most
> and limit building to those ports for which non-default OPTIONS were
> employed.  For me, this is the feature that has always been missing.

Well, there are now "Quarterly" branches.  You should be able to use
pkgs and interlace with built ports seamlessly as long as a quarterly
branch is the source of both.

But yes, using some random binary package set with the latest and
greatest ports trunk is probably going to end badly at some point.

John