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.

Sign up for GitHub

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

Jump to bottom

Reconsider forking frida-mono-api #5

Open
Techbrunch opened this issue Apr 5, 2020 · 1 comment
Open

Reconsider forking frida-mono-api #5

Techbrunch opened this issue Apr 5, 2020 · 1 comment
Assignees
@tijme
Labels
enhancement New feature or request

Comments

@Techbrunch
Copy link
Contributor

I would be nice if frida-mono-api had it's own repo since the original repo does not appear to be maintained anymore.
@tijme
Copy link
Member

tijme commented Apr 6, 2020 •
edited
Loading

I agree that the current situation isn't ideal. Forking would be better indeed. I'll look into it soon. Forking would also improve the UX of Fridax since it wouldn't require including the frida-mono-api by relative path anymore, allowing us to distribute Fridax as an NPM package.

@tijme tijme self-assigned this Apr 6, 2020
@tijme tijme added the enhancement New feature or request label Apr 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tijme tijme

Labels
enhancement New feature or request
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Techbrunch @tijme