Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 9 Nov 2012 10:34:27 -0800 (PST)
From:      Jeffrey Bouquet <jeffreybouquet@yahoo.com>
To:        Beeblebrox <zaphod@berentweb.com>, Chris Rees <utisoft@gmail.com>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: pkgng woes
Message-ID:  <1352486067.114.YahooMailClassic@web164003.mail.gq1.yahoo.com>
In-Reply-To: <CADLo83-bDeqULXf92XGhdq4VUCHc4tD1jz4z7nT3SNb_R5SoCA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
=0A=0A--- On Fri, 11/9/12, Chris Rees <utisoft@gmail.com> wrote:=0A=0A> Fro=
m: Chris Rees <utisoft@gmail.com>=0A> Subject: Re: pkgng woes=0A> To: "Beeb=
lebrox" <zaphod@berentweb.com>=0A> Cc: freebsd-ports@freebsd.org=0A> Date: =
Friday, November 9, 2012, 8:18 AM=0A> On 9 Nov 2012 09:53, "Beeblebrox"=0A>=
 <zaphod@berentweb.com>=0A> wrote:=0A> >=0A> > Pkgng, as a concept may be g=
reat, but it's not really=0A> working - at least=0A> for=0A> > me:=0A> >=0A=
> > 1. pkg2ng conversion does not do a complete job and I=0A> have about ha=
lf of=0A> my=0A> > ports in purgatory or a quasi-installed state. The=0A> p=
rogram runs and is=0A> > installed but pkgdb does not have a record for it.=
 So=0A> my ports updates do=0A> a=0A> > half-ass job.=0A> > 2. I am used to=
 portmaster and I accept that=0A> portupgrade is "more ready"=0A> to=0A> > =
be used with pkgng than portmaster. However, portmaster=0A> has the=0A> > "=
--check-depends" option which I would normally use to=0A> correct problem #=
1,=0A> > alas I see no similar function in portupgrade or pkg.=0A> The "por=
tupgrade=0A> -Ffu"=0A> > and "pkg check" commands don't do the trick either=
.=0A> > 3. I have some ports that I never want to install (like=0A> accessi=
bility/atk=0A> or=0A> > net/avahi). The new pkgtools.conf has a nice featur=
e of=0A> IGNORE_CATEGORIES=0A> > and HOLD_PKGS which I hope will allow me t=
o "blacklist"=0A> those ports but I=0A> > have my doubts as the knob is PKG=
S and not PORTS - so=0A> we'll see.=0A> Separately=0A> > though, while tryi=
ng to get my system pkgng complient=0A> and doing updates,=0A> > there have=
 been some ports which were pulled in that I=0A> whish to remove. As=0A> > =
in #2, portmaster --check-depends did a nice job of=0A> this and allowed th=
e=0A> > dependency to be removed from the portsdb structure -=0A> so same p=
roblem here=0A> > as #2.=0A> > 4. I know how to do +IGNOREME in the portsdb=
 and that=0A> is a very roundabout=0A> > way of solving an sqlite entry.=0A=
> > 5. pkg add does not respect existing port version=0A> information on th=
e=0A> system.=0A> > If you try to install a package and its dependencies,=
=0A> pkg tries to pull in=0A> > its own preferred version. This happened fo=
r perl5 - I=0A> have 5.16 already=0A> on=0A> > the system but pkg kept tryi=
ng to install 5.14. The=0A> only solution was to=0A> use=0A> > the old "pkg=
-add -i" to install one-by-one and without=0A> the dependencies.=0A> > Inte=
resting how pkgng does not have the -i (no-deps)=0A> option??=0A> =0A> Mixi=
ng versions with binary packages is a bad idea=0A> anyway.=A0 Packages are=
=0A> built with a certain set of dependencies, and you can't mix=0A> and ma=
tch (this=0A> has always been the case).=A0 If you want to do this, use=0A>=
 ports.=A0 Packages=0A> are designed to work as a set, hence pkg upgrade ju=
st=0A> upgrades everything=0A> to the latest version.=0A> =0A> Chris=0A> __=
_____________________________________________=0A> freebsd-ports@freebsd.org=
=0A> mailing list=0A> http://lists.freebsd.org/mailman/listinfo/freebsd-por=
ts=0A> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.=
org"=0A> =0A=0ADoes that mean that, for example, when I upgraded a slew of=
=0Apackages ( pkg_add -f ...) that depended upon pkg-config=0Abut installed=
 and theoretically now depending upon pkgconf, that I'd=0Ahave to do them a=
ll by *ports* if using /pkg/ not /var/db/pkg?=0AThat would seriously hinder=
 fully half of my upgrades, making them=0Alast a magnitude of hours longer =
each time... =0A=0AJ. Bouquet



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1352486067.114.YahooMailClassic>