[MacPorts] #40139: frescobaldi @2.0.10

[MacPorts]

#40139: frescobaldi @2.0.10
------------------------------+----------------------
  Reporter:  davide.liessi@…  |      Owner:  g5pw@…
      Type:  submission       |     Status:  assigned
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:
Resolution:                   |   Keywords:
      Port:  frescobaldi      |
------------------------------+----------------------

Comment (by g5pw@…):

 Replying to [comment:11 davide.liessi@…]:
 > Replying to [comment:10 g5pw@…]:
 > > It would be good to depend on lilypond{,-devel}, too, right?
 >
 > I don't think so.
 > Most LilyPond users (at least the ones on the lilypond-user list) prefer
 to download LilyPond.app from the website (which is the advised
 installation method).
 > I would prefer to let the user choose how to install LilyPond.

 Why not instruct MacPorts on how to build Lilypond.app and use that? If
 you let the user choose, are you sure you're not gonna have headaches by
 users installing old lilypond versions, or just users who don't know they
 have to download lilypond.app or install it via MacPorts for Frescobaldi
 to work?

 This just happened to me: I was sure i had lilypond installed via
 macports, I fired up Frescobaldi and tried to build an example file. When
 I pressed Engrave nothing happened. I looked quickly around for any error
 message, but found none. So I labeled it as not working for me. After some
 time, I remember I hadn't installed lilypond after my Mavericks upgrade.
 So, some users will install frescobaldi without installing LilyPond, and
 this will lead to confusion.

 Maybe it's better to investigate why does the users prefer downloading
 lilypond rather than installing through macports.


 > (Frescobaldi will work with any LilyPond installation, and excluding the
 compilation of the source it will work also without a LilyPond
 installation.)
 >
 > By the way, thanks for taking care of this ticket.
 > As soon as a couple of changes will be committed to Frescobaldi, I'll
 update the Portfile (also for the stable version: some bug fixes will be
 back-ported).

 Great, I'll wait for the patches. By the way, the application fails at
 runtime on my machine (MacBook 10.9) with this error:
 {{{
 Traceback (most recent call last):
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/frescobaldi_app/engrave/__init__.py", line 86, in
 engraveRunner
     self.engravePreview()
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/frescobaldi_app/engrave/__init__.py", line 90, in
 engravePreview
     self.engrave(True)
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/frescobaldi_app/engrave/__init__.py", line 127, in engrave
     self.runJob(command.defaultJob(doc, preview), doc)
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/frescobaldi_app/engrave/__init__.py", line 148, in runJob
     jobmanager.manager(document).startJob(job)
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/frescobaldi_app/jobmanager.py", line 62, in startJob
     job.start()
   File
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
 /site-packages/frescobaldi_app/job.py", line 131, in start
     self._process.start(self.command[0], self.command[1:])
 TypeError: arguments did not match any overloaded call:
   QProcess.start(QString, QStringList, QIODevice.OpenMode
 mode=QIODevice.ReadWrite): argument 1 has unexpected type 'bool'
   QProcess.start(QString, QIODevice.OpenMode mode=QIODevice.ReadWrite):
 argument 1 has unexpected type 'bool'
 }}}

 I don't know if it's related to the fact that I don't have LilyPond
 installed.

-- 
Ticket URL: <https://trac.macports.org/ticket/40139#comment:12>
MacPorts <http://www.macports.org/>
Ports system for OS X