[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Packaging git submodule as multi upstream tarballs?



I'm not sure if uscan can do it, but for meshlab, as they don't tag the submodule when they release the main project, I have a script that updates the submodule commit using the github API. It's more clunky than I'd like, but I am not sure exactly how to fix this. It parses the version out of debian/changelog to find the main repo revision. https://salsa.debian.org/science-team/meshlab/-/blob/master/debian/get-orig-source.sh

Ryan

On Tue, Jun 13, 2023 at 10:45 AM Daniel Gröber <dxld@darkboxed.org> wrote:
Hi Mentors,

I'm working on packaging prjtrellis[1] which has a git submodule that is
required for building. My plan is to use dpkg-source's multi upstream
tarball support to do this.

[1]: https://github.com/YosysHQ/prjtrellis

I'm wondering if a) this is a good idea and 2) how to get uscan to download
the precise commit referenced in the main package instead of the "latest"
version. Is this even possible?

I have a similar situation in my yosys package already (it has a
berkeley-abc submodule) but since berkeley-abc is just a seperate package I
just package the latest berkeley-abc commit and pray it doesn't diverge
from what upstream's release uses too much. This is less than ideal
obviously.

Any input would be appreciated,
--Daniel


Reply to: