From owner-freebsd-stable@FreeBSD.ORG Thu Jan 16 16:45:34 2014 Return-Path: Delivered-To: freebsd-stable@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 0B95CD47; Thu, 16 Jan 2014 16:45:34 +0000 (UTC) Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B5D011F07; Thu, 16 Jan 2014 16:45:33 +0000 (UTC) Received: by mail-oa0-f53.google.com with SMTP id m1so1938176oag.26 for ; Thu, 16 Jan 2014 08:45:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pcg8O+TGYi0gi6HoXfmlQswRgeNTBVQx6jrSoURkfF0=; b=TcydAoNcosT8ONnIc7Gz4/fhYIFkW0w73+peaYlztaZpvBZU/dRB01S2x7OR981RqU NhqvTRkohodHkXs0dpdWYUyx20p+tETpotIcGAlkmpc7SpqIKLeIJ2edgWiYX49W1s6T 4C6u39Qr1JutJkWjXEzS++UntnWPDXS0650X7XlcvmUKqhBwq3qbpEuw3L4/DcF0uBkC sUaYztte5AnrVk71BIT4PQTytwiVhPHnqoCYXzI7L4imqkb/rARjjgF5PMr+b67awXqh cPFiFcq9b8cMA71YPCuMtqiMYkR7pYlODYkaFmFiwatowouAtfbL9l7UDVSe9eCBX9XK vXFQ== MIME-Version: 1.0 X-Received: by 10.60.123.10 with SMTP id lw10mr6013509oeb.24.1389890732975; Thu, 16 Jan 2014 08:45:32 -0800 (PST) Received: by 10.76.132.9 with HTTP; Thu, 16 Jan 2014 08:45:32 -0800 (PST) In-Reply-To: References: Date: Thu, 16 Jan 2014 08:45:32 -0800 Message-ID: Subject: Re: FreeBSD 10.0-RC4 pkg upgrade QT conflict From: Freddie Cash To: CeDeROM Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 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:45:34 -0000 On Thu, Jan 16, 2014 at 8:41 AM, CeDeROM wrote: > 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 :-) > I believe a lot of that is planned for future releases, and that 1.3 goes a long way toward that goal (released Real Soon Now). However, I'm not directly involved in the development of pkg, so could be way off in my predictions. :)=E2=80=8B=E2=80=8B --=20 Freddie Cash fjwcash@gmail.com