-
Notifications
You must be signed in to change notification settings - Fork 112
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
How to maintain your own fork of spark? #96
Comments
The idea is that you would clone the repository, track changes from the master branch here (wether you do so in the master branch on your clone, or put them in some other branch), and make your personal changes in a different branch. Then you just merge changes from my upstream master branch to your personal branch. GitHub has documentation on this sort of thing: https://docs.github.com/en/github/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork Ansible is idempotent, so you should be able to just run the playbook again to apply any new additions to your system. Removing old things is a manual process. If I decide to drop a software package from spark, for example, I don't write a task to uninstall it. I just remove the lines from the task that installed it. So you'd have to manually look through the commits for things like that and |
@pigmonkey do you see some automated way to find all packages not installed by spark? And Same for configuration files in |
No. |
Couple of years ago I've cloned spark and have started to have my own changes in repository (because my set of software and settings couldn't be 100% same as somebodies else). From time to time I've cherry-pick`d some commits from upstream. But now I have ~2 years history of commits in upstream I want to incorporate to my fork of spark (and then somehow apply changes with ansible).
So it is more like question and not an issue. What is the best practice?
How to:
The text was updated successfully, but these errors were encountered: