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

Package for elementary OS #240

Open
jtrees opened this issue Aug 4, 2018 · 5 comments
Open

Package for elementary OS #240

jtrees opened this issue Aug 4, 2018 · 5 comments
Labels
wontfix status: wontfix

Comments

@jtrees
Copy link

jtrees commented Aug 4, 2018

elementary OS is a pretty popular distro (according to distro-watch.com). Having the game available on their AppCenter would certainly boost exposure.

https://developer.elementary.io/

@ghost ghost added the help wanted status: help wanted label Aug 4, 2018
@ghost
Copy link

ghost commented Oct 29, 2018

Do you use that distro? Are you packager for that distro? I suppose that's on a rolling release scheme?

@jtrees
Copy link
Author

jtrees commented Oct 29, 2018

I use the distro. I am currently not a packager but I'm willing to explore the options and help you out to get Citadel into the AppCenter.

It's not a rolling release distro. Releases are bound to Ubuntu LTS releases (though they arrive later) so the cycle is every two years. A newest release actually just came out a few weeks ago.

@ghost
Copy link

ghost commented Oct 29, 2018

Even though using Ubuntu LTS as base, if AppCenter itself actually works in rolling release mode, that'd make a very interesting scenario to investigate.

If AppCenter works like the classic Linux distribution model or an LTS model, then the initiative can't succeed:

  • Offline single player is largely unmaintained to the point it can't actually be used as a demonstration pre online mode.
  • As there are only two Argentum Age game servers, beta and mainstream, the online mode requires clients to update arbitrarily. There are at least two ways to do this and none involves the typical model of classic or LTS releases:
    • Require custom built clients to update (as in git pull && make).
    • Distribute client updates via Steam.
    • Use an in house launcher/downloader (currently deprecated).

@jtrees
Copy link
Author

jtrees commented Oct 31, 2018

Phew... I'm not sure I can follow all of that.

AppCenter uses apt under the hood so essentially new versions of a package can be provided by the packager at any time. Users can choose to update to the newest version at will.

Do I understand correctly that this model is unsatisfactory because you wish to require the most recent version for use at all times?

@ghost
Copy link

ghost commented Nov 1, 2018

Phew... I'm not sure I can follow all of that.

[...]

We're here to help.

[...] Users can choose to update to the newest version at will.

Do I understand correctly that this model is unsatisfactory because you wish to require the most recent version for use at all times?

Yes you understand correctly.

@ghost ghost removed the help wanted status: help wanted label Nov 1, 2018
@ghost ghost added the wontfix status: wontfix label Dec 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix status: wontfix
Projects
None yet
Development

No branches or pull requests

1 participant