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

source code? #157

Open
EnderNon opened this issue Aug 6, 2024 · 4 comments
Open

source code? #157

EnderNon opened this issue Aug 6, 2024 · 4 comments

Comments

@EnderNon
Copy link

EnderNon commented Aug 6, 2024

This repo doesn't seem to contain any source code, only the prebuilt binaries. Is Kitsune Mask not open source?

@automorphism88
Copy link

The source code is in a different repository that is linked in the readme.

@EnderNon
Copy link
Author

The source code is in a different repository that is linked in the readme.

As of this time, that repo is 335 commits behind magisk and only 1 commit ahead. That one commit is literally just a japanese translation update. Doesn't seem very real to me

@automorphism88
Copy link

The source code is in a different repository that is linked in the readme.

As of this time, that repo is 335 commits behind magisk and only 1 commit ahead. That one commit is literally just a japanese translation update. Doesn't seem very real to me

I think this fork is just behind — both the source and binary repos. This fork's canary version is at 27001, with last stable release being v26.4, while Magisk Canary is at 27007. That goes for the binaries too, I believe.

I'm currently using a version I compiled from source after cherry-picking one of those commits on top of the source from the source repo, to fix this issue.

Is there some reason to think this binary repo is more up to date than the source repo? If so, please explain.

@EnderNon
Copy link
Author

The source code is in a different repository that is linked in the readme.

As of this time, that repo is 335 commits behind magisk and only 1 commit ahead. That one commit is literally just a japanese translation update. Doesn't seem very real to me

I think this fork is just behind — both the source and binary repos. This fork's canary version is at 27001, with last stable release being v26.4, while Magisk Canary is at 27007. That goes for the binaries too, I believe.

I'm currently using a version I compiled from source after cherry-picking one of those commits on top of the source from the source repo, to fix this issue.

Is there some reason to think this binary repo is more up to date than the source repo? If so, please explain.

my bad, I forgot to check the other branches. Last commit was 2 months ago though, not very great.

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