Re: RFC: optional explicit mapping between orig component name and subdirectory

[Guillem Jover <guillem@debian.org>]

Hi!

On Sat, 2025-12-06 at 10:52:34 +0100, Jérémy Lal wrote:
> Le sam. 6 déc. 2025 à 10:48, Bastien Roucaries <rouca@debian.org> a écrit :
> > Le dimanche 16 novembre 2025, 03:56:00 heure normale d’Europe centrale
> > Simon Richter a écrit :
> > > I'd like to allow packages that have multiple source packages to unpack
> > > them to arbitrary directories in the source tree instead of a fixed
> > > mapping between the .orig archive name and the unpack directory.

> > javascript will love to get this

> > > Opinions?
> 
> Fantastic, this is a missing feature of components.
> 
> How will git-buildpackage deal with this ? Currently we need to explicitely
> set
> component = ['xxx']
> and I suppose gbp import-orig will need to be adapted as well.

The nodejs packages were the bulk of orig addon tarball users I noticed
when scanning the archive, AFAIR. But I'd like to understand what
concrete benefit would we get by adding this backwards incompatible
feature, which could already be used right now (as I mentioned in my
other emails) by convention (just name the addon tarballs as say
"<source>.orig-vendor-node-<module-name>" and then changing dh-nodejs
to use that instead of the current patterns or adapting the files
listing the addons?

Thanks,
Guillem