On Sun, Apr 23, 2017 at 01:04:56PM +0200, Holger Freyther wrote: > Hi, > > for the topic of making "releases" I wondered if we want to explore using > "repo" to tie the different Osmocom repositories into a single "release". > Below is an example "default.xml" that would make up a release. The > default.xml would be maintained in a git repository that we could tag, e.g. > something like v201704.1 (vYYYYMM.MINOR). > > I could envision we have: > > * A simple build shell script to build/install everything > * A script to update (and tag) the default.xml to make new releases available.
I like the central handle on dependencies, but I don't really like XML. Why not use the git submodules approach? Can't submodules tag specific revisions? ~N
signature.asc
Description: Digital signature
