On Mar 22, 2025, at 01:28, Matthias Fechner <mfech...@freebsd.org> wrote:

> Am 21.03.2025 um 16:11 schrieb Mark Millard:
>> 
>>>> It added the following 2 lines to devel/thrift-cpp/pkg-plist :
>>>> 
>>>> lib/cmake/thrift/ThriftConfig.cmake
>>>> lib/cmake/thrift/ThriftConfigVersion.cmake
>>>> 
>>>> The same overall commit also added those lines to each of:
>>>> 
>>>> devel/thrift-c_glib/pkg-plist
>>>> devel/thrift/pkg-plist (Actually this is the creation of this pkg-plist 
>>>> file, it previously did not exist.)
>>>> 
>>>> The conflicts have existed across the 3 since then.
>>>> 
>>>> Someone on discord was trying to use both devel/thrift
>>>> and devel/thrift-cpp , where devel/thrift-cpp would be
>>>> in use in a way that uses what devel/thrift installs.
>>>> 
>>>> 
>>>> cmake related files are installed by the package and 2 of them have the 
>>>> same path
>>>> in 3 different devel/thrift* ports, preventing more than 1 of 3 being 
>>>> installed
>>>> at the same time.
>>>> 
> version 0.14.0 is from 2021.
> Maybe it is an idea to upgrade this to latest version and then check if the 
> problem is fixed upstream?

Note: I got into this helping someone on discord that thought
their poudriere environment was messed up. I'm not a user
of any part of thrift. I just helped identify some of what was
going on in their context.

Also: The notes below are likely more for: komarov_at_valerka.net

Just some general notes . . .

Modern upstream thrift seem to be at 0.21.0 . Most of the ports
with fairly modern official builds are at 0.16.0 from what I
saw on freshports. (I ignore "bump consumers" and other such
changes here.)

0.14.0 is when the transition to cmake happened and when the
file installation conflicts of cmake related files started.
That continued with the updates to 0.16.0 .

At least for 0.16.0 , devel/thrift-cpp and devel/thrift-c_glib
have at least/usr/local/include/thrift/config.h also
conflicting.

I make no claim for if the conflicts should be attributed to
upstream issues vs. to how the partitioning into ports was
structured. I've no clue if having a single version of the
compiler (devel/thift) be used across all the devel/*thrift*
language-specific ports would be reasonable or not.

devel/thrift is the thrift system's compiler producing source
for various langauges from thrift source. devel/thrift-cpp and
devel/thrift-c_glib look to be libraries that the "compiled"
C++ vs. C code depends on, for example. The 3 are far from
being independent conceptually as far as I can tell. I've not
looked at the ties for the likes of devel/py-thrift* or
devel/rubygem-thrift or devel/node-thrift or devel/p5-thrift* .

( devel/pear-Horde_Thrift does not seem to have tracking
version numbers and so might not be related. )

===
Mark Millard
marklmi at yahoo.com


Reply via email to