Subject: Re: Updating pkg_install on NetBSD 4
To: None <pkgsrc-users@NetBSD.org>
From: John Nemeth <firstname.lastname@example.org>
Date: 09/28/2007 04:39:56
On Feb 15, 9:35am, Joerg Sonnenberger wrote:
} On Mon, Sep 24, 2007 at 07:33:09PM +0200, Christian Hattemer wrote:
} > Or maybe include the files that make up the package pkg_install and
} > /var/db/pkg in the base set (or maybe a pkgsrc set), so that a fresh
} > installed system already has one package with the tools installed. However
} > this sounds ugly.
} Why? This is exactly what you get on DragonFly -- the base system and a
} bootstrap from the time the release ISO was built. It is exactly as much
} jumping through holes for users as it is on NetBSD, with the very minor
} difference that updating etc works as updates on pkgsrc are always done.
} Whether this is done by just shipping the binary bootstrap kit as
} additional set or various other possible mechanisms is an entirely
} different question.
Perhaps if you were to detail exactly what this means, we would
have a better basis for discussion. For the sake of argument, let's
say you get to remove pkg_install from base for NetBSD 5.0. Tell the
complete list of steps that a user would need to do after installing
NetBSD 5.0 before they could type 'pkg_add <some random binary
package>' (assume that said package can successfully install and run on
the user's system).
}-- End of excerpt from Joerg Sonnenberger