Harondel J. Sibble wrote: > > On 27 May 2008 at 18:13, stuart wrote: > >> So, here's my thinking: If everyone is running 7.0.x I don't have to >> spend time fixing the code to run older versions. I can go do other >> stuff - yea! >> >> On the other hand, if there are a lot of 6.5.4 and / or 6.3.0 users out >> there, I'll put in some time to at least ensure the mvpmc box does not >> reset. >> >> So... what are you running? > > 6.5.4 here on knoppmyth, I have no intention of upgrading until this hardware > dies or I get around to replacing it. That could be a month from now or a > year from now <shrug>, whoops 6.5.2 actually > > # dpkg -l slimserver > > ||/ Name Version Description > +++-==============-==============- > ============================================ > ii slimserver 6.5.2 Streaming Audio Server >
Ok, this is what I'm going to do. I am going to push my changes (lots of them) where mclient works w/ SqueezeCenter 7.0.1 (never keep changes out too long!). Then I'll set up a 6.5.4 and 6.3.0 server and test them adding code changes and pushing them as I go along. So, if you are running something older than 7.0.x, I would stay put. If you are running 7.0.1 (I would assume you would upgrade to 7.0.1 to catch any SqueezeCenter bug fixes) I would download the daily mvpmc build tomorrow after I put in these new mclient changes and give it a whirl. BTW, if you feel lucky and are running an older server (like 6.5.4 or 6.3.0) try out tomorrow's daily build and post your results / problems. That kind of help I could use! ...thanks ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
