Bleach is a Python module that takes any HTML input, and returns valid,
sanitised HTML that contains only an allowed subset of HTML tags, attributes and
styles. django-bleach is a Django app that makes using bleach extremely easy.
WWW: https://github.com/marksweb/django-bleach
sphinx-design is a sphinx extension for designing beautiful, view size
responsive web components. Created with inspiration from Bootstrap (v5),
Material Design and Material-UI design frameworks.
WWW: https://github.com/executablebooks/sphinx-design
HTML::Escape provides a function which escapes HTML's special characters. It
performs a similar function to PHP's htmlspecialchars. It escapes the following
characters: " & ' < > ` { }
WWW: https://metacpan.org/dist/HTML-Escape
If you've used Moose's native attribute traits, or MooX::HandlesVia before, you
should have a fairly good idea what this does.
Why re-invent the wheel? Well, this is an implementation that should work okay
with Moo, Moose, Mouse, and any other OO toolkit you throw at it. One ring to
rule them all, so to speak.
Also, unlike MooX::HandlesVia, it honours type constraints, plus it doesn't have
the limitation that it can't mutate non-reference values.
WWW: https://metacpan.org/dist/Sub-HandlesVia
Parse::Distname is yet another distribution name parser. It works almost the
same as CPAN::DistnameInfo, but Parse::Distname takes a different approach. It
tries to extract a version part of a distribution and treat the rest as a
distribution name, contrary to CPAN::DistnameInfo which tries to define a name
part and treat the rest as a version.
Because of this difference, when Parse::Distname parses a weird distribution
name such as "AUTHOR/v1.0.tar.gz", it says the name is empty and the version is
"v1.0", while CPAN::DistnameInfo says the name is "v" and the version is "1.0".
See test files in this distribution if you need more details. As of this
writing, Parse::Distname returns a different result for about 200+ distributions
among about 320000 BackPan distributions.
WWW: https://metacpan.org/dist/Parse-Distname
Easy to use and very lightweight module for mocking out sub calls. Very useful
for testing areas of your own modules where getting coverage may be difficult
due to nothing to test against, and/or to reduce test run time by eliminating
the need to call subs that you really don't want or need to test.
WWW: https://metacpan.org/dist/Mock-Sub
DataStruct::Flat converts a nested Perl data structure into a one level hash of
keys and values apt for human consumption.
WWW: https://metacpan.org/dist/DataStruct-Flat
Config::AWS is a small distribution with generic methods to correctly parse the
contents of config files for the AWS CLI client as described in the AWS
documentation.
Although it is common to see these files parsed as standard INI files, this is
not appropriate since AWS config files have an idiosyncratic format for nested
values (as shown in the link above).
Standard INI parsers (like Config::INI) are not made to parse this sort of
structure (nor should they). So Config::AWS exists to provide a suitable and
lightweight ad-hoc parser that can be used in other applications.
WWW: https://metacpan.org/dist/Config-AWS
I missed six months of updates here -- portscout doesn't
seem to find GitLab-based releases for me. The release
notes are on all the tags pages, here's the latest:
https://gitlab.matrix.org/matrix-org/olm/-/tags/3.2.11
Documentation builds now, that seems to be the important
line-item for us this release. 3.2.8 added a better error
description when a buffer is too small. 3.2.7 added better
handling of fallback keys.
mail/procmail-bgrb is a new port tracking the BuGlessRB fork of
procmail (which hasn't been updated for over 20 years).
The commits to BuGlessRB/procmail appear be by the original author
of procmail. Wikipedia documents that the upstream for this port is
its repo.
As this upstream is in active development and the original procmail on
sourceforge is defunct, we may wish to consider merging or replacing
mail/procmail with this port at some point.
Reported by: Lucas Holt at midnightbsd.org (on Twitter)
Try to resolve build issues when generating DOCS. On some systems --
embarrassingly parallel ones, but also seemingly i386 -- the build
happens in a wrong order. This is explained in the comment now
added to the Makefile.
A simple way to trigger the build problem (before this patch) is this:
- configure the port
- switch to the build-dir
- run `ninja -j48 gio-doc`
Dependencies for gio-doc are incomplete, and the build fails.
I tried to solve this at Meson-level, but all my "obvious" changes
to `meson.build` like adding a dependency on `libgdbus_example_objectmanager`
to gio/meson.build got me Meson-time errors. Either no extra dependency
in the resulting Ninja files, or an error that the type of the dependency
was wrong. The ugly way to fix it is to tell ninja -- which does have
a general idea about dependencies between targets -- about it.
