Date: Mon, 04 Nov 2013 20:12:18 +0100 From: =?ISO-8859-1?Q?Lo=EFc?= BLOT <loic.blot@unix-experience.fr> To: freebsd-stable@freebsd.org Subject: Re: pkgng: how to upgrade a single port? Message-ID: <1383592338.13703.0.camel@Nerz-PC> In-Reply-To: <CAOjFWZ4r-gWHd9k8F-T9sE1_5Qa0VVbqzxwYVZGazFf2b0k8VQ@mail.gmail.com> References: <527406D2.7010200@intertainservices.com> <1383336649.16326.41750369.298F8E9D@webmail.messagingengine.com> <1383337118.18823.41752849.2502EBFD@webmail.messagingengine.com> <CA%2BdUSyoUQB%2BgLM8g70y6mz7c%2BHSb3DJpVFvaENgm45VwcYVjQA@mail.gmail.com> <5277E53A.4090208@intertainservices.com> <CAOjFWZ4r-gWHd9k8F-T9sE1_5Qa0VVbqzxwYVZGazFf2b0k8VQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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 ? -- Best regards, Loïc BLOT, UNIX systems, security and network engineer http://www.unix-experience.fr Le lundi 04 novembre 2013 à 10:56 -0800, Freddie Cash a écrit : > On Mon, Nov 4, 2013 at 10:19 AM, Mike Jakubik < > mike.jakubik@intertainservices.com> wrote: > > > 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" > >> > > > > > 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 with a > > pkg you can not choose any options for the port, you have to install with > > 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 it > > wants to re-install just about everything because of a "direct dependency > > changed", im not sure this is correct as it wanted to re-install pkg itself > > just after I freshly installed it from ports. > > > > It's not a limitation in the system; it's a disconnect between how things > work and what you expect. :) > > 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 the > same builds of dependencies, etc. > > 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 everything > 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; always > run a "pkg upgrade" after an update). > > 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 that > you would use the ports tree directly, and compile everything yourself. > > If you want the best of both worlds (ability to configure ports however you > 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 upgraded > in the pkg repo, and which dependencies get upgraded in the local pkg repo, > etc. > > It sounds like poudriere is what you want, not the official pkg repo. > > [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EABEIAAYFAlJ38ZIACgkQh290DZyz8uZIawEAwBtS3JVpdvY9TsoE+JQFHm+l HwkQGNIqb6Q79js4eesBAJx+3PEi6a3YiFkBDCJsK2arFyvskWZ4y8obavFZpQ3A =QBlD -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1383592338.13703.0.camel>