I wanted to swap out my squeezeslave instances with squeezelite as the former is no longer actively developed and also cannot handle Spotify streams.Squeezelite is available on trusty but you have to build it yourself for precise.I went digging to find out how to add it, packages+DT, "the right way" to LMCE.From this effort I have a number of questions;

- I found a git clone on the squeezelite site with additions to support building a deb package. Turns out Uplink did this work. How can this be used by Linuxmce? - To build this deb other packages are required - again not on precise, but available via another PPA, Can these be added with the package manager? - Can DTs be copied? or one based on another?

Just replace the squeezeslave script and adapt the template if required for your use case. Works fine. I suggested using squeezeslave and squeezelite next to eachother some time ago but it was insisted on swapping one for the other. I get so disapointed seeing effort being lost like this when the biggest problem is the amount of development power around lmce.

I've done this by adjusting the script. But this isn't the right way to do it.Squeezeslave could be replaced by squeezelite or I don't see a reason either why they couldn't co-exist - why did they need to be swapped? can you point me to the discussion in the forum?.

The existing template and script could be extended to run either binary - but that adds additional package dependencies that squeezeslave doesn't require.Adding Squeezelite to trusty to coexist with squeezeslave, on the surface, looks manageable.Adding it to precise is that bit harder with the packages not being available from linuxmce/kubuntu repos.

@phenigma - you did a lot of work with the packaging setup and addition of Raspi stuff - can you advise on my initial queries?

There is no technical reason why they could not co-exist. A discussion was had in irc that essentially decided there is no reason to support multiple squeezeslave binaries. One should be chosen to maintain. I had asked for some specifics regarding the changeover. We can build a package for squeezelite on precise, that's not really an issue (imho).

If the squeezeslave binaries are no longer under development then we should migrate to squeezelite.

I wanted to swap out my squeezeslave instances with squeezelite as the former is no longer actively developed and also cannot handle Spotify streams. - I found a git clone on the squeezelite site with additions to support building a deb package. Turns out Uplink did this work. How can this be used by Linuxmce?

There are two ways, we can either build the package in house, or host it in a PPA. I would prefer to build it in house, for precise, and use an ubuntu repo for trusty (if that exists). We would create the package definition and point it to the lmce repo for precise and the ubuntu repos for trusty, easy enough to do. Can you point me to the package (URL)?

- To build this deb other packages are required - again not on precise, but available via another PPA, Can these be added with the package manager?

Likely, but we would do that manually for our builders if posde is okay with that, as well as add the proper dependencies and PPA repos to the database for proper installation of package dependencies. Again, fairly easy.

DTs cannot easily be copied. I would create a new DT with the existing DT open in another window and do it that way. This is how I regurlarily create new DTs that are similar to others.

I hope that helps, I am happy to do some of the integration work but I don't have a lot of time to test right now. I'm around next week then off on vacation for 2 weeks. Let me know if you have other questions!

I would use the existing DT otherwise you will have to change code since lmce needs to know that it is usable for playing audio. Thom pointed me to it and I made the changes but probably did something wrong cause it did not work and I ended up using the existing DT. Since phenigma wants to replace squeezeslave I see even less need to use another DT since otherwise you end up removing the same code afterwards ;-).

If possible please add a optional configuration to be able to specify pulseaudio sinks. Has no influence on the way it works for normal usage and might be useful later on (I use it myself since I run on pulseaudio).

I would use the existing DT otherwise you will have to change code since lmce needs to know that it is usable for playing audio. Thom pointed me to it and I made the changes but probably did something wrong cause it did not work and I ended up using the existing DT. Since phenigma wants to replace squeezeslave I see even less need to use another DT since otherwise you end up removing the same code afterwards ;-).

If possible please add a optional configuration to be able to specify pulseaudio sinks. Has no influence on the way it works for normal usage and might be useful later on (I use it myself since I run on pulseaudio).

We use a separate DT in Dianemo for SqueezeLite as we need to keep existing installations working with Squeezslaves.

There are two ways, we can either build the package in house, or host it in a PPA. I would prefer to build it in house, for precise, and use an ubuntu repo for trusty (if that exists). We would create the package definition and point it to the lmce repo for precise and the ubuntu repos for trusty, easy enough to do. Can you point me to the package (URL)?

Likely, but we would do that manually for our builders if posde is okay with that, as well as add the proper dependencies and PPA repos to the database for proper installation of package dependencies. Again, fairly easy.

No problem. The package definition has been created. The packages are built and available on raspbian wheezy (lmce repo) and on ubuntu trusty (ubuntu repo), I will be added them into ubuntu precise (lmce repo) sometime next week.

No problem. The package definition has been created. The packages are built and available on raspbian wheezy (lmce repo) and on ubuntu trusty (ubuntu repo), I will be added them into ubuntu precise (lmce repo) sometime next week.