Date: Wed, 23 Apr 2003 05:19:09 +0400 From: Sergey Matveychuk <sem@ciam.ru> To: Kris Kennaway <kris@obsecurity.org>, ports@freebsd.org Subject: Re: Recent bsd.port.mk changes Message-ID: <3EA5EA0D.8070500@ciam.ru> In-Reply-To: <20030422193337.GA64963@rot13.obsecurity.org> References: <000501c3074c$e5c2be80$0a2da8c0@sem> <20030421210257.GA58574@rot13.obsecurity.org> <3EA48724.3080602@ciam.ru> <20030422001917.GA60080@rot13.obsecurity.org> <3EA53B4A.4030700@ciam.ru> <20030422193337.GA64963@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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).
In other words, I can't image how it's possible.
> To further complicate matters, ports that are moved from one location
> to another (listed in MOVED, which can be machine-parsed) are also the
> same package, even though they have different origins.
It's more easy to image :)
--
Sem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EA5EA0D.8070500>