Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

missing sources, buildme.sh and build logs #1

Open
klslz opened this issue Dec 31, 2020 · 5 comments
Open

missing sources, buildme.sh and build logs #1

klslz opened this issue Dec 31, 2020 · 5 comments

Comments

@klslz
Copy link

klslz commented Dec 31, 2020

I can't find the sources, buildme.sh (build scripts/processes ) and build logs for the supplied squeezelite binaries.

If these data don't exist, the binaries would have to be replaced and the build data and sources would have to be added.

There are rather new official squeezelite binaries on sourceforge. However, from my point of view, these wouldn't
comply to the usual license terms either.

This plugin would require the same setup as done for the LMS 3pp binaries (flac,sox,etc).

@terual
Copy link
Member

terual commented Dec 31, 2020

This repository is just a copy of the original plugin by Triode. Feel free to submit a pull request!

@michaelherger
Copy link
Member

@terual are the "releases" just copies, too? I was wondering whether I should tweak the plugin to not install/initialize on pCP, as it conflicts with pCP's core feature. But I wouldn't know how to build a release.

@terual
Copy link
Member

terual commented Mar 14, 2024

Yeah, the releases are copies also. When Triodes repo was whut down I downloaded all the release zips. To create this repo I extracted the zips into a this repo and made a commit after each zip extraction to "artificially" create a commit history. I have never made a new release, but it shouldn't be to hard as everything is contained in this repo.

@terual
Copy link
Member

terual commented Mar 14, 2024

Is this the only plugin which conflicts with pCP? If there are more we could maybe add a compatibility flag to the repo xml format which pCP could use?

@michaelherger
Copy link
Member

Is this the only plugin which conflicts with pCP? If there are more we could maybe add a compatibility flag to the repo xml format which pCP could use?

I don't know. And the actual issue that was reported sounded really wrong (LMS starting multiple times). I only thought this plugin didn't make sense in a pCP environment, because pCP is about being a player from the ground up. So there's no need to install this plugin.

But as this was the first time I heard about this issue, I believe we don't really need to do anything anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants