Hello everyone,
When installing a new package (with make install clean) it happens quite often that the install ends up on a conflict, like :
Code:
Installing XXX ...pkg: XXX conflicts with YYY (installs files into the same place). Problematic file: ...
For instance, I've had this problem with mod_fcgid and apache. If there is an upgrade of apache, then the compilation ends on a conflict between mod_fcgid and apache. For this case, I've found this roundabout : first delete mod_fcgid and then upgrade apache and then reinstall mod_fcgid. It works, but it's a bit weird.
And note that :
Code:
# grep mod_fcgid /usr/ports/UPDATING
#
Same problem with texlive now (ports tree installed from portshaker) :
If I do : cd /usr/ports/print/texlive-scheme-full && make install clean, then after a while it ends up here :
Code:
===> Registering installation for texlive-kpathsea-20130112 as automatic
Installing texlive-kpathsea-20130112...pkg: texlive-kpathsea-20130112 conflicts with texlive-core-20120628 (installs files into the same place). Problematic file: /usr/local/share/texmf/web2c/fmtutil.cnf
*** Error code 70
Stop in /usr/ports/print/texlive-kpathsea.
*** Error code 1
Stop in /usr/ports/print/texlive-bibtex.
*** Error code 1
Stop in /usr/ports/print/texlive-scheme-full.
Very strangely, if I rerun make install clean, I get another conflict :
Code:
Installing texlive-texlive-scripts-20130107...pkg: texlive-texlive-scripts-20130107 conflicts with texlive-core-20120628 (installs files into the same place). Problematic file: /usr/local/share/texmf/scripts/texlive/rungs.tlu
*** Error code 70
Stop in /usr/ports/print/texlive-texlive-scripts.
*** Error code 1
Stop in /usr/ports/print/texlive-scheme-full
This situation is a bit confusing. I don't know how to resolve the problem with texlive, there are so many dependencies... I just don't know what to do.
Is there any trick to bypass this kind of problem ? Any option of make that could tell which files to keep, for instance ?
Thanks for any hint !