Open CJ-Wright opened 6 years ago
You can always import a module (.py or .xsh), call a function, etc. If there are common patterns that you are seeing, maybe we could put them in rever or you could always create your own package that your rever.xsh happens to depend on.
It's mostly just the github org, the changelog prepend things.
ie everything is the same except the github org?
The org is the same the project name isn't.
but then everything else is the same?
https://github.com/xpdAcq/xpdAcq/blob/master/rever.xsh vs. https://github.com/xpdAcq/xpdAn/blob/master/rever.xsh
There are some other differences but I could use templating to reduce those changes.
I would write a function that takes the repo / project name and then sets all of the env vars, rather than templating.
That's fair. I can put that function in some central repo which everything depends on.
I mean, you could ever through it in a repo and then have rever.xsh download it and then import/source it :smiley:
I was thinking about using exec :)
Either way!
There is some boilerplate
rever.xsh
things that I use for the XPD stack. What would be the best way to centralize that boilerplate so I don't need to keep writing it? (I imagine some other places would like this as well, eg. conda-forge)