CVS commit: [FLACK_BRANCH] wip/rosegarden-current

[Chapman Flack <jcflack%users.sourceforge.net@localhost>]

Module name:    wip
Tag:            FLACK_BRANCH
Committed by:   jcflack
Date:           Sat Feb  4 22:05:40 UTC 2006

Modified Files:
        wip/rosegarden-current [FLACK_BRANCH]: PLIST distinfo
Added Files:
        wip/rosegarden-current/patches [FLACK_BRANCH]: patch-aa

Log Message:
It's alive. Sort of. After make install, you can run it and get an immediate
dialog box saying it hasn't been installed. That's because some files get
installed in /usr/pkg/share/apps/rosegarden, but the locate("appdata",foo)
function looks instead in /usr/pkg/share/kde/apps/rosegarden. Can't be fixed
with a simple change to --prefix because path components other than the
prefix are involved, and there's probably some kde-specific Right Way to Do
It, and I'll let some kde lover figure it out. I just made a symlink in
/usr/pkg/share/kde/apps pointing to /usr/pkg/share/apps/rosegarden, manually
after install, and that made the stupid dialog go away for me.

The MIDI sequencer will be built to use aRts. aRts 1.4.2 does build on
NetBSD 2.0 and can, on its own, access the MIDI ports: it is possible
to run artscontrol, select Midi Manager, add "OSS MIDI ports", connect
one to another, and successfully pass MIDI data. But the Rosegarden
sequencer exits immediately with a message that ~/.mcoprc may need editing.

docs/howtos/artsd-mcop-notes describes how to edit .mcoprc. The instructions
refer to (a) one file that is in the build tree but does not get installed
anywhere, and (b) one file that does not exist at all. Helpful. The one that
exists can be found as sound/RosegardenMidiRecord.mcopclass. The one that
doesn't can't be found as libMidiArts.la. But there is a MidiArts source file
in sound/ and the object file is part of libRosegardenSequencer.la.

So you might try editing .mcoprc much as the notes suggest, but naming a
directory that contains RosegardenMidiRecord.mcopclass and
libRosegardenSequencer.la. This simply causes artscontrol to crash
immediately Midi Manager is selected from the menu. That's probably
about as much time as I'm likely to spend on that.

Two paths to getting the sequencer working could be (a) debug what's
going wrong in its use of aRts, or (b) clone sound/{Arts,Dummy}Driver
into a new driver specific to NetBSD that just accesses /dev/music
directly and doesn't mess with aRts at all. Given that aRts seems
largely undocumented (a) doesn't appeal much to me, but someone who
knows it might feel differently.

The current release of Rosegarden 4, 1.0, is several releases beyond
this one, and apparently uses an entirely new build system.


To generate a diff of this commit:
cvs -z3 rdiff -u -r0 -r1.1.2.1 wip/rosegarden-current/patches/patch-aa
cvs -z3 rdiff -u -r1.1.1.1 -r1.1.1.1.2.1 wip/rosegarden-current/PLIST
cvs -z3 rdiff -u -r1.2 -r1.2.2.1 wip/rosegarden-current/distinfo

To view a diff of this commit:
http://cvs.sourceforge.net/viewcvs.py/pkgsrc-wip/wip/rosegarden-current/patches/patch-aa?r1=0&r2=1.1.2.1
http://cvs.sourceforge.net/viewcvs.py/pkgsrc-wip/wip/rosegarden-current/PLIST?r1=1.1.1.1&r2=1.1.1.1.2.1
http://cvs.sourceforge.net/viewcvs.py/pkgsrc-wip/wip/rosegarden-current/distinfo?r1=1.2&r2=1.2.2.1

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
pkgsrc-wip-cvs mailing list
pkgsrc-wip-cvs%lists.sourceforge.net@localhost
https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-cvs