Subject: Re: "make install" owerwrites files without asking
To: Jeremy C. Reed <firstname.lastname@example.org>
From: Pavel Cahyna <email@example.com>
Date: 06/27/2005 17:59:43
On Mon, Jun 27, 2005 at 06:52:21AM -0700, Jeremy C. Reed wrote:
> On Sun, 26 Jun 2005, Pavel Cahyna wrote:
> > I installed libxen from pkgsrc-wip and at the end, the following was
> > printed:
> > ===> Registering installation for libxen-2.0.6
> > pkg_create: Overwriting /usr/pkg/include/xc.h - pkg xentools12-040418 bogus/conflicting?
> > pkg_create: Overwriting /usr/pkg/lib/libxc.so - pkg xentools12-040418 bogus/conflicting?
> > This warning was not very useful, because those files belonging to
> > xentools12 were already overwritten when it was printed.
> > Shouldn't the check for conflicting files be performed before the actual
> > installation, instead of after it? Currently, a package without explicit
> > conflict can damage other installed packages, which seems wrong to me.
> It could be a little difficult to check this using pkgsrc, but possible.
> One way would be to create wrappers for all INSTALL_* scripts, cp, mv,
Why??? I looked at the PLIST for libxen and all the information needed to
prevent this problem was there: