prjtrellis-db being a seperate repo without any release tags is problematic for (Debian) packaging. Our current upstream-source-download tools are deficient in that there isn't a palatable way to get git-submodule commit information into the packaging workflow.
The main problem being that in most traditional distro packaging everything revolves around tarballs, so we just don't even have the submodule commit ID available to us at all and versions have to be matched manually.
It would help tremendously if prjtrellis-db had release tags that coincide with the main repo's tags, i.e. since prjtrellis v1.4 pulls in [database/ @ ce8cdaf] prjtrellis-db should have a tag v1.4 pointing at ce8cdaf.
Hi,
prjtrellis-db being a seperate repo without any release tags is problematic for (Debian) packaging. Our current upstream-source-download tools are deficient in that there isn't a palatable way to get git-submodule commit information into the packaging workflow.
The main problem being that in most traditional distro packaging everything revolves around tarballs, so we just don't even have the submodule commit ID available to us at all and versions have to be matched manually.
It would help tremendously if prjtrellis-db had release tags that coincide with the main repo's tags, i.e. since prjtrellis v1.4 pulls in
[database/ @ ce8cdaf]prjtrellis-db should have a tagv1.4pointing atce8cdaf.Thanks, --Daniel