- Reference packages with <pkg> tag
- Unify flag descriptions by removing trailing dot from first two flags
- Restrict glade and gnomecanvas flag to <dev-ml/lablgtk-3,
dev-ml/lablgtk:3 uses sourceview use flag only
Signed-off-by: Petr Vaněk <arkamar@atlas.cz>
Closes: https://github.com/gentoo/gentoo/pull/28564
Signed-off-by: Sam James <sam@gentoo.org>
Per bug #881383, string replacing forms of parameter expansion must take care
to quote - or appropriately escape - any nested parameter expansions, assuming
that their values are intended to be taken literally (as is almost invariably
the case). This has long been the case, but the introduction of the new
patsub_replacement option in bash >=5.2 has brought the issue to the fore.
In the case of the app-editors/jupp package, the improper quoting is not yet
causing any issues. Still, it is better to write the code properly to begin
with, especially considering the demonstrative value of robust code.
Signed-off-by: Kerin Millar <kfm@plushkava.net>
Bug: https://bugs.gentoo.org/881383
Signed-off-by: Sam James <sam@gentoo.org>
Per bug #881383, string replacing forms of parameter expansion must take care
to quote - or appropriately escape - any nested parameter expansions, assuming
that their values are intended to be taken literally (as is almost invariably
the case). This has long been the case, but the introduction of the new
patsub_replacement option in bash >=5.2 has brought the issue to the fore.
In the case of the app-dicts package category, the improper quoting is not yet
causing any issues. Still, it is better to write the code properly to begin
with, especially considering the demonstrative value of robust code.
Signed-off-by: Kerin Millar <kfm@plushkava.net>
Bug: https://bugs.gentoo.org/881383
Signed-off-by: Sam James <sam@gentoo.org>
Per bug #881383, string replacing forms of parameter expansion must take care
to quote - or appropriately escape - any nested parameter expansions, assuming
that their values are intended to be taken literally (as is almost invariably
the case). This has long been the case, but the introduction of the new
patsub_replacement option in bash >=5.2 has brought the issue to the fore.
In the case of the net-vpn/networkmanager-strongswan package, the improper
quoting is not yet causing any issues. Still, it is better to write the code
properly to begin with, especially considering the demonstrative value of
robust code.
Signed-off-by: Kerin Millar <kfm@plushkava.net>
Bug: https://bugs.gentoo.org/881383
Signed-off-by: Sam James <sam@gentoo.org>
Per bug #881383, string replacing forms of parameter expansion must take care
to quote - or appropriately escape - any nested parameter expansions, assuming
that their values are intended to be taken literally (as is almost invariably
the case). This has long been the case, but the introduction of the new
patsub_replacement option in bash >=5.2 has brought the issue to the fore.
Note that, in this instance, it's actually a command substitution injected into
the replacement 'string' that merits quoting.
Signed-off-by: Kerin Millar <kfm@plushkava.net>
Bug: https://bugs.gentoo.org/881383
Signed-off-by: Sam James <sam@gentoo.org>
Per bug #881383, string replacing forms of parameter expansion must take care
to quote - or appropriately escape - any nested parameter expansions, assuming
that their values are intended to be taken literally (as is almost invariably
the case). This has long been the case, but the introduction of the new
patsub_replacement option in bash >=5.2 has brought the issue to the fore.
In the case of the games-util/game-device-udev-rules package, the improper
quoting is not yet causing any issues. Still, it is better to write the code
properly to begin with, especially considering the demonstrative value of
robust code.
Signed-off-by: Kerin Millar <kfm@plushkava.net>
Bug: https://bugs.gentoo.org/881383
Signed-off-by: Sam James <sam@gentoo.org>
It's only for silencing the "no KEYWORDS" warnings, now that we have
~loong on the ebuild it's about time to drop it because the ebuild
actually isn't pulling from VCS.
Suggested-by: Michał Górny <mgorny@gentoo.org>
Signed-off-by: WANG Xuerui <xen0n@gentoo.org>
It's only for silencing the "no KEYWORDS" warnings, now that we have
~loong on the ebuild it's about time to drop it because the ebuild
actually isn't pulling from VCS.
Suggested-by: Michał Górny <mgorny@gentoo.org>
Signed-off-by: WANG Xuerui <xen0n@gentoo.org>
It's only for silencing the "no KEYWORDS" warnings, now that we have
~loong on the ebuild it's about time to drop it because the ebuild
actually isn't pulling from VCS.
Suggested-by: Michał Górny <mgorny@gentoo.org>
Signed-off-by: WANG Xuerui <xen0n@gentoo.org>
It's only for silencing the "no KEYWORDS" warnings, now that we have
~loong on the ebuild it's about time to drop it because the ebuild
actually isn't pulling from VCS.
Suggested-by: Michał Górny <mgorny@gentoo.org>
Signed-off-by: WANG Xuerui <xen0n@gentoo.org>