xcbuild conflicts with libplist

[ryandesign (Ryan Carsten Schmidt)]

$ sudo port install xcbuild
--->  Computing dependencies for xcbuild
--->  Fetching archive for xcbuild
--->  Attempting to fetch xcbuild-0.1.1_0.darwin_16.x86_64.tbz2 from https://packages.macports.org/xcbuild
--->  Fetching distfiles for xcbuild
--->  Verifying checksums for xcbuild
--->  Extracting xcbuild
--->  Configuring xcbuild
--->  Building xcbuild
--->  Staging xcbuild into destroot
--->  Installing xcbuild @0.1.1_0
--->  Activating xcbuild @0.1.1_0
Error: Failed to activate xcbuild: Image error: /opt/local/lib/libplist.dylib is being used by the active libplist port.  Please deactivate this port first, or use 'port -f activate xcbuild' to force the activation.
Error: See /opt/local/var/macports/logs/_Users_rschmidt_macports_macports-ports_devel_xcbuild/xcbuild/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port xcbuild failed
elapsed: 00:02:13

[seanfarley (Sean Farley)]

Thanks for the report! I wonder if xcbuild could use libplit.

[seanfarley (Sean Farley)]

In eab19bce/macports-ports:

xcbuild: mark conflicts with libplist

Closes: #53381

[cooljeanius (Eric Gallager)]

I'd prefer to see this conflict actually fixed by putting the conflicting libraries in a subdir or something, rather than just marking the conflict. Checking the contents of the xcbuild destroot makes it look like there are some other libraries that might conflict with stuff there, too