-
Notifications
You must be signed in to change notification settings - Fork 21
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
Put lrc-server on a linux remote repository. #31
Comments
The best way to do this would be to create archives for the major distributions (such as Ubuntu, Debian, Fedora, ...) and to submit it to the package maintainers. This way, the server could easily be installed via |
That is the idea. |
lrc-server in official repositories would be awesome. I'll look forward to that :) |
You can also create your own repository with reprepro it is really easy! I saw that you already have your website, so if you can upload files in there it is all you need! (Plus it will be a signed repository) I did it for my software and i find it really useful. Each time that i build a deb package, i have an lftp script that synchronizes my local repository with the online. ( it makes you win a lot of time :) ) You will have also the advantage that users won't have to use apt-get -f install to get the dependencies, and each time that you update your online repo they will get notified on synaptic/the ubuntu pacakge manager :) __ |
Sweet, good idea ! If you're interested in contributing on this project, I made a huge pull-request that basically changes all the backend for the server-client communication, but that version is buggy, so we can't use it yet. It would be nice to have more people contributing on this project ! -- By the way, |
I was thinking in a way to auto-update the lrc-server to user.
And i think that linux remote repositories is a good option.
I need see the best way to do this, if use a PPA or a official repository like of the Ubuntu.
Anyway, what do you think of this ?
The text was updated successfully, but these errors were encountered: