[Bug 274889] devel/py-setuptools_scm7: conflicts with devel/py-setuptools_scm

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 04 Nov 2023 14:28:05 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274889

John Hein <jcfyecrayz@liamekaens.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|Works As Intended           |FIXED

--- Comment #3 from John Hein <jcfyecrayz@liamekaens.com> ---
(In reply to Matthew Seaman from comment #2)
"py-setuptools_scm{,7} are by their nature only used as BUILD_DEPENDS"

Indeed.  But there are a few ports have RUN_DEPENDS that list
py-setuptools_scm.  None (yet) list py-setuptools_scm7.  When that happens, it
will be a real problem (because conflicting run-time deps can't be installed
together - also a port that has build-time depends on two ports that conflict
on scm{,7} can be a problem even in poudriere).  I understand these are things
you likely already know, but for posterity of this bug, I'll just put that
notion into writing. Your comment is generally correct for most uses of
setuptools_scm, of course.

When I first opened this bug I thought there was a run-time dependency that
existed on py-setuptools_scm7 (and that was not/is not yet the case).

We'll cross the conflicting run-time dependencies bridge when we get to it (if
ever).

Some examples of ports with RUN_DEPENDS listing py-setuptools_scm:

devel/py-b2sdk
devel/py-flit-scm
devel/py-hatch-vcs
devel/py-pyscaffold
devel/py-setuptools_scm_git_archive
textproc/py-python-lsp-jsonrpc

Some of those may be wrong (i.e., not actually run-time deps, just build-time).

-- 
You are receiving this mail because:
You are the assignee for the bug.