Closed daxgames closed 4 years ago
Cool. I'm for this.
One addition, though, can you define PREFIX?=
after the other variables in the beginning of the makefile and add a comment which mentions that it's used to prefix the targets? This way people whom surf through the Makefile can immediately see any variables that are used/customizeable.
Sorry it took me a bit to follow up on this, was afk for a few weeks and apparently can't get Internet where I live, so it's hard for me to test things at the moment. Heh.
@arizvisa Done.
Merging.
User customization without forking
Note: Does not affect existing
make
commands ifPREFIX
is not set.Users can clone boxcutter/windows and make user specific copies of Packer templates, scripts and configs they can edit that are ignored by git.
*.json
template files can be symlinks to files in another repo.floppy
andscript
cannot be symlinks but can be links to files in other repos.This adds flexibility to customize and to easily sync with the upstream repo at any time!
$(PREFIX)
to theMakefile
make PREFIX=[company]. [company].[target]
to build from[company].target.json
.gitignore
floppy and script folders:*.*.json
floppy/*.*.*
script/*.*.*
I use it as follows:
I have a repo in Github with my customizations that are business specific:
I can now use boxcutter/windows unmodified with my user customizations that have no business being in your repo and everything is still in source control.
I think this is a great add to this project for users that need user customizations and don't want to fork and keep their personal repo synched with this repo.