Qball Cow <[EMAIL PROTECTED]> wrote: > Hi people, Hi Qball,
> Just a quick fix for an api-breakage in git. > With commit 6dcd7fea (if I am not mistaken) the error returned when you > try to save to an existing playlist is wrong. > Instead of MPD_ACK_ERROR_EXIST, MPD_ACK_ERROR_NO_EXIST is returned. This > is obviously wrong and breaks gmpc. > > Appended is a small patch to fix this. Thanks, applied. > Furthermore I would like to request, once again, a way for the client to > see if the/a playlist(s) have changed. > Now there is no way for me to detect if another client modfied, added or > removed a playlist. How often is this a problem? Given that we've had the current implementation for 5 years with few complaints that I know of, I'd rather just do it properly with the listener protocol in the next few months than a one off in the next few days... > 2nd thing is, what are we going todo to the spam on this dev list? is > shank the only one with access to the mailinglist settings?o My client-side filters are pretty good. Other than that, I we could complain to SF.net and hope they care... > 3rd thing, is there a roadmap? I want to make one for gmpc, but without > one for mpd.... Last one I posted was here, I'll try to update it over the weekend http://thread.gmane.org/gmane.comp.audio.musicpd.devel/176 > 4th thing, what is going to happen with normalperson and cirrus mpd > version. As client developer I am getting nervous seeing two separate > branches I have to support. Because there are different plans as of > features to implement in mpd this will be a problem for me in the future. Max and I can both be quite difficult to work with at times. We're both very opinionated and feel strongly about mpd. I see his ideas as far too complex and verbose and I have little time/patience to deal with many of them. I'll continue to feed him some ideas and take ideas from him that I consider sound and try to work on a consistent interface for the clients to see. Unfortunately his branch is more and more difficult to merge with as time goes by as our ideas often clash and diverge. Regardless, a mix of choice, competition and collaboration is still a good thing; and having an automated protocol test suite would go a long way towards keeping compatibility. I have zero plans on breaking compatibility with older clients (and please bug me if I do!) > 5th. What is the current state of mpd? when will there be a next > release? See 3rd question... I'm hoping for sometime in November... Some of my other projects have been unfortunately neglected lately, and it looks like I'll be out of town the last week of October for GitTogether. > 6th. What are we going to do with the mpd website? No idea... > 7th. What is the state of the 30% cpu usage, alsa output bug? I kind of > lost track of it. But the reports people still make, it is still an issue. My attempted fixes were both shots in the dark and didn't fix the issue. From what Max gathered, it seemed to be dependent on the kernel timer used. > 8th. Should we setup an automated "mirror" of git on f.e. repo.or.cz? of > mpd/libmpdclient/ncmpc etc? Both Max and my mpd branches are on repo.or.cz. Everything is up to the individual branch owners since repo.or.cz has automated pull. If I do any significant work on libmpdclient/mpc in the future; I'll also put those on repo.or.cz, too. > 9th. Normalperson is it possible to setup an automated mirror of my > repos on git on git.musicpd.org?? Yes. Send me the URLs you want mirrored and mirror frequency and I'll set it up tomorrow or over the weekend. Also, if you want push access, let me know (and send me your public SSH key), too. -- Eric Wong ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
