libmemcached xercesc3: resolve conflict

[petrrr]

libmemcached and xercesc3 are declared conflicting. This conflict should be resolved instead.

Ports xercesc and xercesc3 are different versions of the same software, so the conflict is probably acceptable. libmemcached is a very different software and should become installable along with xercesc3.

The conflict apparently caused by one single file and the non-case-sensitive filesystem:

• xercesc3: /opt/local/bin/MemParse
• libmemcached: /opt/local/bin/memparse

Any proposals how to resolve this?

[petrrr]

Ping? Any news on this one?

[petrrr]

Hi, is this port abandoned? Please express your interest in this port explicitly.

[scantor (Scott Cantor)]

xercesc3 is definitely not abandoned, but I don't know the best way to resolve the conflict. A new version of xerces is coming shortly so I could probably do something then, if I have some suggested approach to follow. Given the lack of importance of the MemParse program, is deleting it post-install inside the port enough to resolve the conflict, or will that not do it?

[petrrr]

Sorry for not being precise: I did not refer the products itself, but was wondering if it was abandoned by the maintainers. This ticket was not acknowledged for quite some time and snc has not reacted to many tickets. So I am considering to file a port abandoned ticket.

libmemcached currently has no maintainer.

[scantor (Scott Cantor)]

NP, just providing context. It so happens though that my ultimate port on top of xercesc3, shibboleth, can make use of libmemcached, and I'm maintaining the xercesc3 port and free to change it, so if it solves the conflict, I'm willing. Just wanted to know if I do a delete action after the install step runs, will that prevent the conflict?

[nerdling (Jeremy Lavergne)]

Replying to petr@…: Yes, we can delete the MemParse program in xercesc3 but I certainly would not have done so without scantor's approval.

[scantor (Scott Cantor)]

We might also just do a glob rename and prefix all the bins with Xerces. That's probably more future proof and less drastic than deleting anything.

[scantor (Scott Cantor)]

I've updated the xercesc3 port to 3.1.2, but have not had a chance to test the conflict fix. This is a security release in part, so I wanted to get it out immediately, but I will work on a revision of the port that renames the binaries in the near future.

[scantor (Scott Cantor)]

Port revised to rename bin files, and the conflict removed.

[petrrr]

Thanks a lot!