Hi Simon,
On Sun, 24 Aug 2025 22:02:27 +0900 Simon Richter wrote:
> I'm just trying to use git-modules, and it doesn't do anything. Looking
> into the source code, it seems that this is handled only when making
a new
> clone, not when being called from a checkout.
>
> That's probably not much of a valid use (although there is special
handling
> for using the current checkout otherwise), so minor severity. Having at
> least a warning would be nice though.
git-modules only supports cloning from a repository at this time, as I
didn't expect anyone to run uscan from an existing git directory.
I believe you are referring to the code path in the git.pm module? [1]
Anyway, based on your report, is the following scenario correct?
* You have already cloned a git repository, which contains one or more
submodules.
* The submodules are active and cloned from the remote repository. I
believe `git checkout` only operates on active submodules, but we could
probably initiate them from uscan if not already active.
* uscan should create the tarball from the current path.
If not, please provide more detail.
Thanks,
Hugh
[1]
https://salsa.debian.org/debian/devscripts/-/blob/main/lib/Devscripts/Uscan/Modes/Git.pm?ref_type=heads#L98
