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

Extract supportings source code into custom repositories #3003

Closed
Ash258 opened this issue Jan 17, 2019 · 1 comment
Closed

Extract supportings source code into custom repositories #3003

Ash258 opened this issue Jan 17, 2019 · 1 comment

Comments

@Ash258
Copy link
Contributor

Ash258 commented Jan 17, 2019

To keep this repository cleaner and more relate, it should be shrinked from not needed files (not talking about bucket folder, that's tracked somewhere else). Supporting folder can contains only binaries of each utility, not whole source code, with all project files. (Better management of changes, release page for better updating of them, ...)

Extract validator and shimexe into scoopinstaller github organization. (SideNote: Please rename it to use PascalCase or at least first upper character; it looks better)

Some kind of script for updating them will be required, but it should be only scoop like "installation" into this supporting folder, which would be executed manually. It could be done on user side, but I can't think about best way how to do it. Best solution I can think of is just keep it inside repository to reduce / eliminate error domain.

I would really appreciate this extraction / script to handle getting yaml library without some git tree / submodules way.

@Ash258
Copy link
Contributor Author

Ash258 commented Jan 17, 2019

Extraction should be possible even with history: https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/

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