Hi,

considering that it makes sense to settle with DEP14[1] first before we
can decide about DEP18 I wonder what is finally needed to accept DEP14.
I think its cruxial to make git-buildpackage supporting DEP14 per
default[3] but I'm somehow sensing some hen-egg problem here what to do
first.  If DEP14 might be accepted the motivation to fix bug #829444
would be probably way higher.

Just a personal note: All repositories where I'm uploader (>1000) are
following git-buildpackage default layout and thus not compatible with
the DEP.  So accepting DEP14 would mean a lot of work for me (at least
testing the suggested scripting solutions[4] carefully) and for my
personal workflow I'm not really keen on pushing DEP14.  However,
wearing my DPL hat with the clear intention to streamline common
workflows, I'd be happy if we would move forward here.

Are there any blockers to accept this DEP which I might have missed?

Kind regards
    Andreas.

[1] https://dep-team.pages.debian.net/deps/dep14/
[2] https://salsa.debian.org/dep-team/deps/-/merge_requests/8
[3] https://bugs.debian.org/829444
[4] https://lists.debian.org/debian-devel/2020/09/msg00168.html
    https://lists.debian.org/debian-devel/2020/09/msg00172.html

-- 
https://fam-tille.de

Reply via email to