Conflict on very first port (xorg) on rpi3

[Mark Millard]

On 2020-May-15, at 00:33, Mark Millard <marklmi at yahoo.com> wrote:

> bob prohaska fbsd at www.zefox.net wrote on
> Fri May 15 04:30:07 UTC 2020 :
> 
>> An attempt to compile x11/xorg on a new installation of 12.1 on a Pi3B resulted in a
>> conflict:
>> 
>> ===>  Installing for py37-sphinx18-1.8.5_1,1
>> ===>  Checking if py37-sphinx18 is already installed
>> ===>   Registering installation for py37-sphinx18-1.8.5_1,1 as automatic
>> Installing py37-sphinx18-1.8.5_1,1...
>> pkg-static: py37-sphinx18-1.8.5_1,1 conflicts with py37-sphinx-3.0.2,1 (installs files into the same place).  Problematic file: /usr/local/bin/sphinx-apidoc-3.7
>> *** Error code 70
>> 
>> Had this been the umpteenth port compiled, I'd understand somewhat. 
>> 
>> As the _very_ first port compiled, I'm confounded......
>> Uname -a reports
>> FreeBSD nemesis.zefox.com 12.1-STABLE FreeBSD 12.1-STABLE r361020 GENERIC  arm64
>> Svnlite info /usr/ports reports:
>> Path: /usr/ports
>> Working Copy Root Path: /usr/ports
>> URL: 
>> svn://svn.freebsd.org/ports/head
>> 
>> Relative URL: ^/head
>> Repository Root: 
>> svn://svn.freebsd.org/ports
>> 
>> Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
>> Revision: 535263
>> Node Kind: directory
>> Schedule: normal
>> Last Changed Author: jkim
>> Last Changed Rev: 535263
>> Last Changed Date: 2020-05-14 20:52:33 -0700 (Thu, 14 May 2020)
> 
> Both textproc/py-sphinx18 and textproc/py-sphinx require
> the following to have been built and installed already
> in order to build:
> 
> lang/python37
> devel/py-setuptools at py37
> 
> textproc/py-sphinx18 requires 3 more ports as well:
> 
> devel/py-Jinja2 at py37
> textproc/py-docutils at py37
> devel/py-six at py37
> 
> Some building and isntalling had to occur prior to the
> textproc/py-sphinx18 build attempt, possibly from
> prior session(s) of building and installing.
> 
> 
> textproc/py-sphinx18 is new as of 2020-May-11.
> The devel/llvm[16789]0 ports require textproc/py-sphinx18 .
> Only about 26 ports require textproc/py-sphinx18 but
> I'll not list the others.
> 
> textproc/py-sphinx has been around longer and has
> 142 ports that require it. I'll not list them.
> 
> 
> textproc/py-sphinx18/Makefile lists:
> 
> CONFLICTS_INSTALL=      py*-sphinx
> 
> textproc/py-sphinx/Makefile lists:
> 
> CONFLICTS_INSTALL=      py*-sphinx18
> 
> 
> So, for example, indirectly the devel/llvm[16789]0
> ports conflict with at least 142 other ports because
> of the textproc/py-sphinx* difference in requirements.
> 
> 
> The conflict is real and limits what combinations
> of ports you may have installed at the same time.


Note: I only counted "required for build", not
"required for run" in my counts of "Require" status.
(I also ignored deleted ports.)

I'll note that devel/poudriere style building of
ports should allow building without having the
conflict (separate jails for each build, each
with its own, local /usr/local/ like area).

But Makefile use, portmaster use, and the like
probably see the conflict because of installing
everything built someplace under (typically)
the system's /usr/local/ and leaving the
installation there.

Only 4 ports require textproc/py-sphinx18 "for
run". 20 ports require textproc/py-sphinx "for
run". devel/llvm[16789]0 do not require either
"for run", just "for build". But that still
leaves the conflict to manage unless a tool with
poudriere-like properties is used to build them.


===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)