Dear Guy, 2013/9/16 Guy Stalnaker <jimmyg...@gmail.com>: > Tonight I tried to use your new port. The port compiles with no errors. The > macport install process failed when attempting to activate your > Frescobaldi+devel saying that previous files exist.
I'm sorry I didn't notice this problem on my machine before the publication of my Portfiles. I had manually installed Frescobaldi and python-poppler-qt4 but not with Philippe's guide: I had installed them explicitly setting the prefix to something different from /opt/local, so they didn't interact with MacPorts' directory hierarchy. This problem occurs because when you do "python setup.py install" for python-poppler-qt4 and Frescobaldi, they are installed inside the directory tree of the Python version you used (in this case the MacPorts' one). So their files are copied inside MacPorts' tree. When you then install them with my Portfiles, MacPorts tries to copy the same files in the same locations, but it finds the manually installed files and refuses to continue. This is because manually installed files can be user data files (e.g. databases) or user settings files (like the ones in /opt/local/etc), so by default MacPorts cannot overwrite files that weren't written by itself. Philippe is right when he says that 2013/9/16 Philippe Massart <phili...@philmassart.net>: > The idea is to really avoid touching manually the macport tree. The solution, that Philippe mentions, should be simply to force the activation with '-f' option. This allows MacPorts to overwrite existing files. 2013/9/16 Guy Stalnaker <jimmyg...@gmail.com>: > I did a check by > attempting to deactivate Frescobaldi, but macports said there was not an > activated Frescobaldi port. MacPorts was right: there wasn't an active Frescobaldi or python-poppler-qt4 port, but it couldn't activate them because there were already files in place. 2013/9/16 Philippe Massart <phili...@philmassart.net>: > Now, the errors you have when trying to open files come probably from the > folders you moved. Probably. The best thing to do, in my opinion, is to uninstall frescobaldi(-devel) and py27-python-poppler-qt4 ports, move back the folders and files in their original location and then force install frescobaldi(-devel). This way all other ports should work correctly and the force install should take care of overwriting the manually installed files. 2013/9/16 Philippe Massart <phili...@philmassart.net>: > Like you, I had a manually installed frescobaldi version; since "forcing" > the activation of the portfile, my both frescobaldi install are now working: > the one from macport, the other manually installed (and sync via github). As long as you don't "python setup.py install" Frescobaldi (with the default prefix) there shouldn't be interaction problems between MacPorts and manually installed versions. My advice is to avoid "python setup.py install" for Frescobaldi at all and run it from its directory. You can rely on MacPorts for all dependencies (including python-poppler-qt4) and then have MacPorts' Frescobaldi and, e.g. in your home directory, multiple directories each with a different version of Frescobaldi (or a Git repository in which you can switch versions). Dear Guy, let us know if you need further assistance and if the "undo move / force install" solution works for you. I think I should put a notice on my repository's home page about this problem, but I'll wait and see if the proposed solution works for you. Best wishes. Davide _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
