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

Proposed TODO: Tool sources should be their own repository(ies) #712

Open
PikalaxALT opened this issue Dec 11, 2018 · 1 comment
Open

Proposed TODO: Tool sources should be their own repository(ies) #712

PikalaxALT opened this issue Dec 11, 2018 · 1 comment

Comments

@PikalaxALT
Copy link
Collaborator

Motivation: We currently have copies of the tools included in ruby which are required by other agb decompilations (emerald, firered, berry fix, mmbn6). There is a need to keep these tools synchronized across repositories to ensure consistency between users and contributors regardless of when they cloned the respective projects.

Suggestion 1: Repurpose pokeruby-tools to provide the sources rather than static Windows binaries, and submodule it.

Suggestion 2: Create new repositories for each individual tool, and submodule each.

@PikalaxALT
Copy link
Collaborator Author

WIP in emerald implements a third solution which would establish a package manager for the tools and install them to a custom path in the system root.

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

1 participant