#33179: xymon and xymon-server disagree about whether clientlaunch.cfg should be registered to the port or not -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: fclaire@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: xymon -------------------------------------+-------------------------------------- Comment(by fclaire@…): Thanks for reporting this problem. xymon and xymon-server packages conflict each other and only one should be installed on a given machine. The workaround is to remove the directories ${prefix}/lib/xymon and ${prefix}/var/log/xymon. This behavior is coming from the way config files are managed. I followed what's recommended here: https://trac.macports.org/wiki/PortfileRecipes#configfiles "The current solution is to rename any config files to append a .dist or .sample extension to them so that the proper name of the config file is not part of the port." I'm doing this in the post-destroot phase: {{{ post-destroot { xinstall -d -o ${xymonuser} -g ${xymongroup} ${destroot}${xylogdir} xinstall -d -o ${xymonuser} -g ${xymongroup} ${destroot}${xytmpdir} # Adding a suffix to config files foreach f { clientlaunch.cfg localclient.cfg xymonclient.cfg } { move ${destroot}${xyetcdir}/${f} ${destroot}${xyetcdir}/${f}.${version} } } }}} Is it the wrong phase ? Why does the port believes the original .cfg file belong to the other xymon port ? When will #2365 be closed ? -- Ticket URL: <https://trac.macports.org/ticket/33179#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS