Date: Wed, 27 Oct 2021 09:00:21 +0000 From: Alexey Dokuchaev <danfe@freebsd.org> To: Stefan E??er <se@freebsd.org> Cc: ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: 00e15405660f - main - textproc/html2text: Update CONFLICTS Message-ID: <YXkVJfKXVfb%2BzYR9@FreeBSD.org> In-Reply-To: <202110270841.19R8fLH2046856@gitrepo.freebsd.org> References: <202110270841.19R8fLH2046856@gitrepo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 27, 2021 at 08:41:21AM +0000, Stefan E??er wrote: > commit 00e15405660fffeb44772bd58ff17e841d71729b > > textproc/html2text: Update CONFLICTS > > The CONFLICTS definition did only match conflicting packages built > for Python-2.7, not for later Python versions. > > I have not checked whether CONFLICTS_INSTALL would suffice as used > in the conflicting ports. The PORTREVISION has not been bumped since > this parameter is relevant for port building, less so for installing > from a package (which detects the conflicting files). Somewhat surprisingly, CONFLICTS are not recorded in package manifests; given the existence of `pkg_conflicts' table in /var/db/pkg/local.sqlite which is always empty, it was probably planned, but never implemented. > ... > -CONFLICTS= py27-html2text-[0-9]* > +CONFLICTS= py*-html2text-[0-9]* I recal, last time I've tried to specify a conflict without the -[0-9]* suffix and it worked as expected. Are those really necessary in default "all versions" case? ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YXkVJfKXVfb%2BzYR9>