Packaging may or may not be done in another repository, depending on how the conundrum on handling binary blobs is handled by me. I will be handling the packaging for RHEL based distributions i.e. Fedora/Korora and CentOS/Scientific Linux/RHEL-EPEL.
If packaging is to be done for other distros, someone else will have to handle that.
Update LICENSE and README files to reflect the goals of this fork:
Goals:
Why fork it?
What types of contributions will be accepted?
Re-iterate that this is an unofficial and unsupported fork i.e. support should not be sought from the Emby community.
Stance on circumventing the subscriber only features offered by Emby premiere. Hint: this project is definitively against that - those features can/should be purchased from emby.media i.e. the upstream developers more than deserve to be compensated for their work irrespective of whether I disagree with their licensing.
Stance on removing advertisements for upstream subscriber-only features. Hint: this project is definitively against that.
Remove third party binary blobs from this repository.
Remove Emby LLC proprietary binary blobs from this repository.
Implementation:
Where possible obtain these from NuGet.
2a) Replace these with dummy libraries, just throw not implemented. This will allow the new 'EmbyServer' implementation to build unencumbered.
2b) Within the new EmbyServer implementation add a method that checks whether the assembly properties contain the word 'Dummy', if they do then download those binaries from upstream and replace them before sigterm'ing the process and starting it back up.
2c) Not sure how friendly this is to the GPL... might implement passing a parameter containing the upstream repository url and handle the passing of that in packaging which would be done in a separate repo under a seperate license.
Emby.Sync is making an a request to an unidentified server and receiving a http 500 response. Going to need to examine the content of the request to ascertain what's supposed to be happening.
It's throwing a non critical exception at the moment.
I am a windows guy and I have serious issues on how to go about complying. I don't mind installing Fedora or Debian. even if i manage to build i don't think i might know how to run the project. I can cope if I have a wiki
It appears as though the upstream netcore package not only does not have the updated project files published, but also there is also a application host project that's not being published in the repository.
That project "EmbyServer" needs to be re implemented, in order to run Emby. It's going to take some time to do this.
Hello,
i'm trying to do make command after clone but i have this error:
/tmp/Emby/MediaBrowser.sln.metaproj : error MSB3202: il file di progetto "/tmp/Emby/Emby.Server.Unix/Emby.Server.Unix.csproj" non è stato trovato. [/tmp/Emby/MediaBrowser.sln]