Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Philippe Massart]

Hello,

Before trying to find a solution to your situation (it will take some time to investigate), I think interesting to point some possible explanations about what occurred.

I think that to problem comes from the coexistence of macport installed frescobaldi, and manually installed (even with with macport dependencies): some libraries (python-poppler-qt4, mainly) make a link between frescobaldi and other dependencies. If these are installed by macports, a file is created in the macport install tree. That's why it says that a file already exists when trying to activate the "macport frescobaldi". The problem is not frescobaldi itself, but the link with the dependencies.

Usually, a macport message error mentions a solution: "force the activation" (something like "sudo port -f activate frescobaldi-devel). Macport then makes a copy of the former link file and allows the link between the dependencies and the "macport installed" frescobaldi (I sent a message to the list about that).

Now, the errors you have when trying to open files come probably from the folders you moved. I don't remember if there is a feature like "rebuild" in macport, but the first things I would do in this case would be:

- repair authorisation

- re-install macport :/ (or at least remove frescobaldi (the macport version) and the dependencies you don't use (to uninstall frescobaldi and its dependencies without removing the dependencies used by other ports, I think the command looks like sudo port -fellow-dependencies frescobaldi-devel Double check in the help of macport)

The idea is to really avoid touching manually the macport tree.

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).

Hope this could help (at least for further investigations)

Philippe

Le 16 sept. 2013 à 04:17, Guy Stalnaker <address@hidden> a écrit :

Davide,

Prior to using your new port, I had a working Frescobaldi that I installed many months ago using a very cryptic and painful process that required a lot of manual work to get poppler, frescobaldi, etc installed. But, it did work.

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 did a check by attempting to deactivate Frescobaldi, but macports said there was not an activated Frescobaldi port. So I systematically renamed each file/folder using the mv comment as the port activate process for your new Frescobaldi port kept throwing up the errors. Eventually your port successfully activated.

And, it runs. But any attempt to open a file results in a cascade of errors. First set seem related to code-folding. Then there are more and eventually Frescobaldi crashes.

Now quite sure how to fix this. If macports said that there was no previous port I don't know how it could remove/clean it to make way for your port. Nor do I know enough to use a terminal (which I do know how to use) to remove things manually. Easy enough to use 'mv path path.old' as the port install was tossing out errors. Not so much to ferret out all the possible things that may be hindering your new port.

Any suggestions welcome.

Guy Stalnaker
address@hidden

_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user