DragonFly BSD
DragonFly users List (threaded) for 2005-04
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: Stable tag will be slipped Sunday and release engineering will begin Monday

From: walt <wa1ter@xxxxxxxxxxxxx>
Date: Mon, 4 Apr 2005 17:44:57 -0700

On Mon, 4 Apr 2005, David Rhodus wrote:

> On Apr 4, 2005 11:16 PM, walt <wa1ter@xxxxxxxxxxxxx> wrote:
> > The task of *upgrading* a collection of such ports has lagged behind in pkgsrc,
> > at least as implemented in NetBSD-current.

> I track several different packaging systems daily and I've found that
> pkgsrc actually tends to update their major packages(KDE, GNOME, XORG,
> etc...) faster some of the other systems available today for DFly.

If I take your meaning correctly (always a danger) I am not criticizing
pkgsrc because the *versions* of popular packages lag behind -- not at all.

The speed with which the *versions* of packages are updated is entirely
dependent on the number of skilled volunteers, not on the packaging system.

I would hope that pkgsrc offers the promise (eventually) that the pool of
skilled labor working on such version updates will be united, instead of
fragmented (as it is at present).

My complaint (so far as I feel entitled to complain about something I get
for free) is that NetBSD's pkg_chk -u is (most often) a disaster for me.

Any time a gnome package is updated, all dependencies are deleted immediately
(without asking me first) and then (more often than not) one of the replacement
packages fails to compile -- leaving me with a pile of smoking rubble instead
of a functional machine.

This is a good chance for me to asK:  is pkg_chk part of the pkgsrc project?

If not, what alternatives does pkgsrc offer to pkg_chk and portupgrade?

These are absolutely critical questions for me and, I suspect, for others.

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]