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

Is it safe to use one of the tags for packaging? #3

Open
hwittenborn opened this issue Jun 21, 2022 · 3 comments
Open

Is it safe to use one of the tags for packaging? #3

hwittenborn opened this issue Jun 21, 2022 · 3 comments

Comments

@hwittenborn
Copy link

I'd like to start packaging this minecraft launcher for Debian, and I'm looking into getting everything compiled correctly. I saw that the last commit was made in March of 2021, but the latest tag is only from December of 2018. Is there a reason the latest tag is so old in comparison to the latest commit?

@ChristopherHX
Copy link
Member

ChristopherHX commented Jun 24, 2022

I created a tag for the current used version should be save to use now.
However I still need to investigate why xbox sign in broke in 2021. This component is unused for Minecraft 1.16.20+ and is not needed for xbox sign in anymore.

I stopped packaging deb in 2020 due to lack of an apt repository.

@hwittenborn
Copy link
Author

This component is unused for Minecraft 1.16.20+ and is not needed for xbox sign in anymore.

So I don't need to package this if I want to package the launcher?

@ChristopherHX
Copy link
Member

Yes you don't need package it, It's optional. Only required for xbox live <= Minecraft 1.16.10, you can select that old versions from the versions picker of the launcher and they open if they are >= 1.13 in v0.3.4

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

2 participants