Nicholas D Steeves dixit:
>Sorry for the extremely belated reply. I did read your reply soon after
>you sent it :)
No problem, we are all doing this in our spare time…
>Ah, now I see what you mean about 4.x being upstream focus.
They focus on it to the exclusion of 3.x support. It was similar
in the late stages of 3.x alphas for 2.x, but not as bad; they had
a working 2.x and users wanted fixes, and they gave them fixes, but
this resulted in 3.0 being delayed for over a year so they didn’t
want to repeat it. (Of course, 4.0 is still very much away, so it’s
obviously not (just) that…)
>If I run into a bug then I'll dig for new commits.
Thanks! Same here, I have a few queued up and just noticed an
error for the status line when capodaster is used which I’ll fix
since the status line code is from me (and the capo code apparently
was slapped on without fixing internal pitch housekeeping).
>> • parts of the playback functionality is now a “freeware” binary
>> add-on plugin only available from their in-program download store
>
>Wow, that plugin doesn't sound very nice... I wonder why it can't be
>released under a dfsg-compatible license?
Ostensibly (the formal answer I got to this when asking on the .org
forums) because “that would then require the sound libraries to also
be open-sourced”, which is obviously wrong. I called Daniel Ray out
on it but he never answered. Months later in an interview for Scoring
Notes, he’s indicated it is so they can use it in a commercial product
of Muse Group where the playback engine is basically the USP of their
iOS äpp, vs competitor äpps. So he lied, as I thought.
>Yes, I completely agree; This sounds like a case where the Debian model
>of a stable base plus backported fixes results in a more reliable tool
>than running the latest available release.
I agree, and most users agreed when I explained this to them.
Those who need chord playback or those other rare new-in-3.x features
can use the chords-to-notes plugin or use the upstream-provided
containerised images, which upstream promotes over the packaging
efforts anyway. (I feel underappreciated sometimes. I hinted at
licence compatibility problems for these, but I don’t really want
to stick time into *that* given the Debian packages are fine.)
>Also, it sounds like it will
>be best to wait for the future-4.x series' first beta before starting to
>work on a musecore4 package.
>
>Would you please consider keeping this bug open in case other people
>wonder why things are the way they are with Musescore in Debian?
Sure!
bye,
//mirabilos
--
> Hi, does anyone sell openbsd stickers by themselves and not packaged
> with other products?
No, the only way I've seen them sold is for $40 with a free OpenBSD CD.
-- Haroon Khalid and Steve Shockley in gmane.os.openbsd.misc
