From owner-freebsd-stable@FreeBSD.ORG Mon Nov 4 19:01:14 2013 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 ESMTP id F242F5D3 for ; Mon, 4 Nov 2013 19:01:13 +0000 (UTC) (envelope-from loic.blot@unix-experience.fr) Received: from smtp.institutoptique.fr (smtp2.institutoptique.fr [194.199.220.151]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 75FE82B3E for ; Mon, 4 Nov 2013 19:01:12 +0000 (UTC) Received: from [10.42.69.5] (ASt-Lambert-152-1-5-6.w82-124.abo.wanadoo.fr [82.124.35.6]) by smtp.institutoptique.fr (Postfix) with ESMTPSA id EC6F126159 for ; Mon, 4 Nov 2013 20:01:04 +0100 (CET) Message-ID: <1383592338.13703.0.camel@Nerz-PC> Subject: Re: pkgng: how to upgrade a single port? From: =?ISO-8859-1?Q?Lo=EFc?= BLOT To: freebsd-stable@freebsd.org Date: Mon, 04 Nov 2013 20:12:18 +0100 In-Reply-To: References: <527406D2.7010200@intertainservices.com> <1383336649.16326.41750369.298F8E9D@webmail.messagingengine.com> <1383337118.18823.41752849.2502EBFD@webmail.messagingengine.com> <5277E53A.4090208@intertainservices.com> Organization: UNIX Experience Fr Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-RHLBAPnY8p5Otli5inS3" X-Mailer: Evolution 3.10.1 Mime-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: loic.blot@unix-experience.fr List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2013 19:01:14 -0000 --=-RHLBAPnY8p5Otli5inS3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Upgrading a single port can be useful. Yaourt on archlinux permit to edit a text file to remove packages we doesn't want to remove, why not do like it ? --=20 Best regards, Lo=C3=AFc BLOT,=20 UNIX systems, security and network engineer http://www.unix-experience.fr Le lundi 04 novembre 2013 =C3=A0 10:56 -0800, Freddie Cash a =C3=A9crit : > On Mon, Nov 4, 2013 at 10:19 AM, Mike Jakubik < > mike.jakubik@intertainservices.com> wrote: >=20 > > On 11/03/13 17:24, George Kontostanos wrote: > > > >> You can alway lock a package or the packages that you don't need to > >> upgrade. See: "pkg help lock" > >> > > >=20 > > Thanks for the info but that would be very tedious to do. Is it just me= or > > is this a gross oversight of this new pkg system? Also the fact that wi= th a > > pkg you can not choose any options for the port, you have to install wi= th > > options that the port maintainer chose. As it stands now if i do pkg > > upgrade it wants to pull in a bunch of stuff that i do not want, also i= t > > wants to re-install just about everything because of a "direct dependen= cy > > changed", im not sure this is correct as it wanted to re-install pkg it= self > > just after I freshly installed it from ports. > > >=20 > It's not a limitation in the system; it's a disconnect between how things > work and what you expect. :) >=20 > The official packages are built using the default options for each port, > and they are created in a single batch. They are designed to be upgraded > all at once so that everything is from the same compilation run, using th= e > same builds of dependencies, etc. >=20 > It's expected that you will either never update the local repository file > (ie, never run "pkg update" and add -U to all commands) so that everythin= g > is installed from the same repo version; or that you will specify a > specific date in the repo path; or that you will upgrade everything in > lock-step with the repo (always run "pkg update" before an install; alway= s > run a "pkg upgrade" after an update). >=20 > If you want the most flexibility in how ports are configured, ability to > install a single port, upgrade a single port, etc, then it's expected tha= t > you would use the ports tree directly, and compile everything yourself. >=20 > If you want the best of both worlds (ability to configure ports however y= ou > want; ability to upgrade indibidual ports; not have to compile everything > for every little change; etc) then you want to look into > ports-mgmt/poudriere. That allows you to create local pkg repos of > packages built however you like. And you control when a port gets upgrad= ed > in the pkg repo, and which dependencies get upgraded in the local pkg rep= o, > etc. >=20 > It sounds like poudriere is what you want, not the official pkg repo. > =E2=80=8B=E2=80=8B >=20 --=-RHLBAPnY8p5Otli5inS3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EABEIAAYFAlJ38ZIACgkQh290DZyz8uZIawEAwBtS3JVpdvY9TsoE+JQFHm+l HwkQGNIqb6Q79js4eesBAJx+3PEi6a3YiFkBDCJsK2arFyvskWZ4y8obavFZpQ3A =QBlD -----END PGP SIGNATURE----- --=-RHLBAPnY8p5Otli5inS3--