Got some replies from upstream dev
"You can get a tarball from a tag on github. Plus, I thought all packagers have been doing things straight from git (no tarballs) for like half a decade now. I can't remember the last time I touched a tarball..."
"Never gonna happen. To much work to manage."Maybe it would be worth asking upstream if they would be willing to split out the different applications into different git repositories? It wouldn't be that hard to do.
Different versions numbers is not a major problem I think, but I've little experience with it of courseIf they are not willing, then we need to decide how to do the packaging. We could: 1. Package directly from the git repository, using a version number that reflects the git commit that was used for the package, build all of the applications (which I think was the default in the build system) and install them into separate binary packages. This would mean the version number doesn't match the different version numbers of the different applications.
2. Separately download each tarball into separate source packages all watching the same repository for new tarballs. 3. Other options???
I asked if it would be a idea to package NSM without the non-toolkit first, so with FLTK:
"Totally reasonable. Again, I'm 99% sure that NSM's GUI doesn't use any NTK specific features or controls."
This would mean that 'we' would package NSM with FLTK first, and leave Non-Daw for later. For me and the community, NSM is the most important.
Regards,
\R