Subject: Re: is there still need for devel/bmake and devel/mk-files?
To: Julien T. Letessier <firstname.lastname@example.org>
From: Julio Merino <email@example.com>
Date: 06/08/2003 00:57:53
On Sun, 8 Jun 2003 00:37:00 +0200 (CEST)
"Julien T. Letessier" <firstname.lastname@example.org> wrote:
> On Jun 6, 2003, at 21:33, Julio Merino was heard saying:
> > I think we could do like what debian does with its base system. That is,
> > the bootstrap-pkgsrc .tgz could contain a package database registering the
> > packages in it (like bmake, pax, etc). This way, after you have unpacked
> > it, if you run pkg_list you could see what's already installed (bootstrap
> > packages) and update them when needed. The only problem with this is that
> > the package database should be placed inside the tgz (i.e., inside PREFIX
> > and not /var)...
> In fact, the eventual bootstrap-pkgsrc .tgz would already contain a package
> database. The current process registers the 'digest' package -- so my
> bootstrap tarballs come with this one package already registered.
> This brings up an issue: on non-NetBSD systems, having the boostrap tools
> registered as packages possibly causes the system to shoot itself in the foot:
> what about 'pkg_delete pax' on a machine that doesn't have eitheir 'tar' or
There is something in pkgsrc to specify that a given package cannot be
uninstalled, iirc. (Jeremy? I think you use it.)
Julio M. Merino Vidal <email@example.com>
The NetBSD Project - http://www.NetBSD.org/