On Mon, Jun 04, 2018 at 02:05:34AM +0100, Stuart Henderson wrote: > > Basically, fetch the -current ports tree > (http://www.openbsd.org/anoncvs.html), > make whatever changes, and run "cvs diff". > > For sending in mail, copy-and-paste from a terminal will likely mangle it > (whitespace may change e.g. tabs/spaces), some people use "xclip" > (cvs diff | xclip) and paste into mail, some people redirect to a file > (cvs diff > /tmp/lmms.diff) and include that instead. > I updated my ports tree but I have been working in a mystuff dir and perhaps that is not best for doing a diff > > Go to https://lmms.io/download/ or https://github.com/LMMS/lmms/releases > and you'll see that the latest is 1.2.0-rc6. > > The "stable-1.2" tree on github is actively being developed on the path > towards 1.2.0, rc6 was tagged from that tree a few days ago. > > I've just asked upstream if they'd mind rolling tarballs and adding them > to the release (https://github.com/LMMS/lmms/issues/4400) as that would > make life easier. > OK if we can use and rc that is better than rolling back to 1.1.3 which is less than desirable. > > Either of these: > > - build it as normal, but don't install it. Either patch in the port > Makefile to rm zyn-related files, or @comment in pkg/PLIST. > > - patch lmms to disable building it. > I have had issues with it building if Zyn is even included for the build. But I may be misremembering at what step it gave up.
> Did it not build, or did it build and not run (and if so, what happened)? > It did start for me and I was able to play demo tracks etc. > To rule out patching-related problems I'll attach a tar of my port directory > if you fancy giving that a spin (move the old directory out the way before > untarring as it removes some old files). I'll send the diff in-line as > well for anyone who wants to test in the usual way. I've updated it to > 1.2.0-rc6 and patched out zynaddsubfx build now. > If I remember right it did not build, but I might not have had everything. I will try out what you attached to this email > > They seem pretty close to 1.2.0 so sometime after that would be a good > natural point to actually update it in ports. There doesn't seem to > be much point in looking at an older version than 1.2. Typically we > wait for a stable release (rather than updating to a release candidate) > though that's not a hard rule. > That seems sensible. I am not in a rush, I just want to be able to use it (which I can personaly building it) and also do what I can to contribute. > > It needs patching - libossaudio isn't used for audio io on OpenBSD, there are > a couple of remaining users in ports but I believe they're just for some > volume-control-related function. Certainly it shouldn't be added to anything > else. I have patched that in my update. > > I found it is easy enough to patch by editing the CMakelist.txt file. Ken P.S. Thanks for your guidance and patience with me as I try to get acclimated to the OpenBSD way of doing things.
