Roland Mas <[email protected]> wrote:
> Le 25/12/2025 à 14:20, Edward Betts a écrit :
> > * Package name    : dh-removebadges
> >    Version         : 0.1
> > * URL             : https://salsa.debian.org/debian/dh-removebadges
> > * License         : GPL-3+
> >    Programming Lang: Perl
> >    Description     : debhelper addon to remove remote badges and external 
> > images from documentation
> > 
> >    This debhelper addon automatically removes remotely-hosted images (such 
> > as
> >    build status badges, coverage badges, version badges from shields.io, 
> > GitHub,
> >    GitLab, etc.), iframes, and tracking scripts from documentation files in 
> > the
> >    package source tree.
> 
> That's a great tool :-) May I suggest expanding the scope to also handle the
> repetitive task of replacing the CDN links with local versions for common
> JS/CSS libraries, such as Bootstrap and Jquery? That would probably require
> injecting the appropriate dependency so as to use the system-installed
> version, and should be written such that adding new replacement patterns
> doesn't require rewriting code. Maybe the libjs-* packages themselves could
> provide the patterns and the replacements, and dh-removebadges (if it keeps
> that name) could parse these provided files as well as its own and act
> accordingly.

Hi Roland,

Thanks for your message, much appreciated.

I really like that suggestion, and it fits neatly with the motivation behind
the tool. The more I think about it, the more it feels like this wants to be
broader than just badges. I'm leaning towards renaming it to dh-doc-privacy,
with the scope being "remove or replace privacy-unfriendly external resources
in documentation".

Replacing CDN links for common JS/CSS libraries with system-installed versions
is a great example of that. One possible approach would be to start by
handling the most common cases (jQuery and Bootstrap), then later evolve it
towards your idea of libjs-* packages providing patterns and replacement
metadata.

Your message has definitely nudged me towards thinking bigger about the
problem space.

Cheers,

Edward

Reply via email to