[MacPorts] #45722: libmemcached xercesc3: resolve conflict
#45722: libmemcached xercesc3: resolve conflict --------------------+----------------------------------- Reporter: petr@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: libmemcached xercesc3 --------------------+----------------------------------- `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? -- Ticket URL: <https://trac.macports.org/ticket/45722> MacPorts <https://www.macports.org/> Ports system for OS X
#45722: libmemcached xercesc3: resolve conflict ------------------------------------+------------------- Reporter: petr@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libmemcached xercesc3 | ------------------------------------+------------------- Comment (by petr@…): Ping? Any news on this one? -- Ticket URL: <https://trac.macports.org/ticket/45722#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#45722: libmemcached xercesc3: resolve conflict ------------------------------------+------------------- Reporter: petr@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libmemcached xercesc3 | ------------------------------------+------------------- Comment (by petr@…): Hi, is this port abandoned? Please express your interest in this port explicitly. -- Ticket URL: <https://trac.macports.org/ticket/45722#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#45722: libmemcached xercesc3: resolve conflict ------------------------------------+------------------- Reporter: petr@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libmemcached xercesc3 | ------------------------------------+------------------- Comment (by scantor@…): 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? -- Ticket URL: <https://trac.macports.org/ticket/45722#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#45722: libmemcached xercesc3: resolve conflict ------------------------------------+------------------- Reporter: petr@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libmemcached xercesc3 | ------------------------------------+------------------- Comment (by petr@…): 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. -- Ticket URL: <https://trac.macports.org/ticket/45722#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
#45722: libmemcached xercesc3: resolve conflict ------------------------------------+------------------- Reporter: petr@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libmemcached xercesc3 | ------------------------------------+------------------- Comment (by scantor@…): 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? -- Ticket URL: <https://trac.macports.org/ticket/45722#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
#45722: libmemcached xercesc3: resolve conflict ------------------------------------+------------------- Reporter: petr@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libmemcached xercesc3 | ------------------------------------+------------------- Comment (by snc@…): Replying to [comment:4 petr@…]: Yes, we can delete the MemParse program in xercesc3 but I certainly would not have done so without scantor's approval. -- Ticket URL: <https://trac.macports.org/ticket/45722#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X
#45722: libmemcached xercesc3: resolve conflict ------------------------------------+------------------- Reporter: petr@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libmemcached xercesc3 | ------------------------------------+------------------- Comment (by scantor@…): 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. -- Ticket URL: <https://trac.macports.org/ticket/45722#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X
#45722: libmemcached xercesc3: resolve conflict ------------------------------------+------------------- Reporter: petr@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libmemcached xercesc3 | ------------------------------------+------------------- Comment (by scantor@…): 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. -- Ticket URL: <https://trac.macports.org/ticket/45722#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X
#45722: libmemcached xercesc3: resolve conflict ------------------------------------+-------------------- Reporter: petr@… | Owner: snc@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libmemcached xercesc3 | ------------------------------------+-------------------- Changes (by scantor@…): * status: new => closed * resolution: => fixed Comment: Port revised to rename bin files, and the conflict removed. -- Ticket URL: <https://trac.macports.org/ticket/45722#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X
#45722: libmemcached xercesc3: resolve conflict ------------------------------------+-------------------- Reporter: petr@… | Owner: snc@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libmemcached xercesc3 | ------------------------------------+-------------------- Comment (by petr@…): Thanks a lot! -- Ticket URL: <https://trac.macports.org/ticket/45722#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts