Recent bsd.port.mk changes

Kris Kennaway kris at obsecurity.org
Tue Apr 22 23:48:16 PDT 2003


On Tue, Apr 22, 2003 at 10:33:09PM -0400, Joe Marcus Clarke wrote:
> On Tue, 2003-04-22 at 21:32, Kris Kennaway wrote:
> > On Wed, Apr 23, 2003 at 05:19:09AM +0400, Sergey Matveychuk wrote:
> > > Kris Kennaway wrote:
> > > >features enabled ("foo-1.2.3" vs "foo-esound-1.2.3" etc.)  This is why
> > > >I suggested that comparing the installation prefix and pkg-plist for
> > > >overlap with ports that have the same origin may be the only way to do
> > > >this reliably.
> > > 
> > > I don't know how to compare pkg-plist files? How to make decision a port 
> > >  is older version and not variant of current one? It must be some 
> > > evristic method. Some files can be moved in other place, some files can 
> > > be new, some files can be moved away in new version.
> > > In port's variant case path can be changed or file name can be changed 
> > > (libsome.so and libsome_r.so).
> > 
> > You can extract the prefix from the installed package by grepping for
> > @cwd in +CONTENTS.
> 
> Or you can use pkg_info -p -q ${PKGNAME} which is what the patch I sent
> you uses.
> 
> >   Similarly you can extract the list of installed
> > files by doing grep -v ^@ +CONTENTS.  
> 
> pkg_info -f -q ${PKGNAME} should provide this.

OK, cool.  I didn't realise these existed.

> > For each package that has our
> > origin (or a previous origin as looked up in the MOVED file), do the
> > following: if the installed prefix == $PREFIX and one or more of the
> > installed files matches a file in pkg-plist (checked using
> > e.g. comm(1)), then we are going to conflict and we should not
> > install.  I can't immediately think of how to implement the installed
> > plist extraction without using a temporary file, but it should be
> > possible with some thought.
> 
> I can try to modify the patch I sent you to do this check as well.  It
> already does the ${PREFIX} check.

I'm getting confused by multiple patches flying around :-) It looks
like yours has some technical features I had overlooked, although I
wasn't sure about the need for deinstall-all after the later
discussion.  Could you and Sergey come up with something that handles
all the problem cases we've talked about?

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20030422/83514abd/attachment.bin


More information about the freebsd-ports mailing list