Subject: Re: pkg/23719: pkg_install package can't be created
To: Eric Haszlakiewicz <email@example.com>
From: Jeremy C. Reed <firstname.lastname@example.org>
Date: 12/12/2003 13:34:33
On Fri, 12 Dec 2003, Eric Haszlakiewicz wrote:
> > PKG_PRESERVE is good enough. It was implemented to get rid of those other
> > restrictions. The NO_PKG_REGISTER and NO_PACKAGE should be removed.
> well, then unless someone has some reason to keep those, I'm going to
> commit that change.
You may also want to look at same issue with archivers/pax and
> > (My other problem is lack of db related functionality with pkg_install
> > tools.)
> eh? could you be talking about the same reason that I don't get a
When pkg_install is configured it checks for:
checking for dbopen...
Have a look at "HAVE_DB" in lib/pkgdb.c.
Under BSD/OS it configures and works; but under Linux for me, it
A dependency on a db package was not wanted for the pkg_install package.
Someone needs to get pkg_install to build with the lib/libdb2.a on all
platforms. And then maybe it could just use databases/db/buildlink2.mk.
(It needs to be buildlinked, but only as a build-time BUILD_DEPENDS
Not having db support is bad for me, because my custom pkg_install's
upgrade option uses the list of filenames to know what files aren't in new
install to delete them from system.
Jeremy C. Reed