From owner-freebsd-stable@FreeBSD.ORG Thu Jan 16 16:41:26 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 88573866; Thu, 16 Jan 2014 16:41:26 +0000 (UTC) Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 349D01E9F; Thu, 16 Jan 2014 16:41:26 +0000 (UTC) Received: by mail-qa0-f48.google.com with SMTP id f11so2327140qae.35 for ; Thu, 16 Jan 2014 08:41:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=9iy3NMjG086UPSUcpgct7LwawTw77b4wK4S+BEgTsxo=; b=uxwdRIzOEQ7isE2YaINkZB4jv4re1S8i3Qlc/kjEL48nN0n/SYJ1e/zx/pPPSd9n/h 2I7AXCBxzTmo+4IWGJNUohnqXVpL1jNgY7o7bAkkXqNb4m6yTu6VXg9C+ZdAGJRZC72x xaWeZ4o/Wa7GuxniKtfMX/pqhkRayXaoU9Hg4HRmqwxPL1r3BfJqzEr9JdK88dEoD6NT vIZ4VZiAQAnz2Vu3YxcW86cY43U3tcLN2+yDzvpavqXg3FkWyocDmj1609/owc551aqd LA7hW9yPFAfzMO74rSeW9a8JpQrwVJPNOL7x/eLSbqsmYHTuCEdwkWqsFqaIreh9ylAk 1t5A== MIME-Version: 1.0 X-Received: by 10.224.42.197 with SMTP id t5mr17608306qae.57.1389890485313; Thu, 16 Jan 2014 08:41:25 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.229.151.73 with HTTP; Thu, 16 Jan 2014 08:41:25 -0800 (PST) In-Reply-To: References: Date: Thu, 16 Jan 2014 17:41:25 +0100 X-Google-Sender-Auth: KIqw9NhzNZQw3KL7i-zQCwt5m90 Message-ID: Subject: Re: FreeBSD 10.0-RC4 pkg upgrade QT conflict From: CeDeROM To: Freddie Cash Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Stable , freebsd-ports X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jan 2014 16:41:26 -0000 Hello and thank you for all suggestions :-) What I mean is that PKG seems to be missing some "good" mechanism for such conflict solution... and this situation WILL happen as users will want to rebuild custom options of packages from a different port tree. I have compiled by hand hpijs with network backend as my HP use JetDirect and this is disabled by default. Because I have compiled a port with WITH_PKGNG I assumed that PKG will be engaged and take care of proper dependency management or refuse to install as this would break binary dependencies tree. I was wrong. I also assumed that PKG will manage to handle port renames, dependency changes, etc. I was wrong. +1 for PKG to be able to handle such situations either by simply forcing to set port tree to version that would allow safe build (bad for new ports, simple solution), or calculate dependencies so they won't break current binary tree when newer ports are installed (good for new ports, complex work for pkg) :-) Long story short - there should be no conflict situation when I install updated port build by hand :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info