Subject: Re: /var/db/pkg
To: Peter Seebach <email@example.com>
From: Johan Ihren <firstname.lastname@example.org>
Date: 05/22/2000 21:22:10
email@example.com (Peter Seebach) writes:
> In message <20000522135651.A15896@noc.untraceable.net>, Andrew Brown writes:
> >>>>Shouldn't this be /usr/pkg/var/db/pkg?
> >>>i think /usr/pkg/etc/pkg would be better, but that's just me...
> >>Either way, I think it should be in /usr/pkg. In an ideal world, a tarball
> >>of /usr/pkg should be self-contained and portable.
> >portable? if you mean portable modulo endianness and architecture,
> >then yes. otherwise, no.
> Agreed; I just mean between machines. It should be fairly rational
> to tarball /usr/pkg on one system, untar it on another, and expect
> success. Currently, the result is bogus unless you also move some
> of /var/db.
Speaking of which: to me it's bogus with an ".install_done" file in
the pkgsrc work-directory. Whether a package is installed or not is
recorded in /var/db/pkg (or possibly /usr/pkg/ wrt to the above
discussion), not in the source/build tree.
The rest of the status files, like .build_done etc, are fine, it's
just the .install_done that annoys me.
Johan Ihrén, <firstname.lastname@example.org>,
phone: +46 (8) 790 6844, Center for Parallel Computers,
Royal Institute of Technology, SE-100 44 Stockholm, Sweden