Age | Commit message (Collapse) | Author | Files | Lines |
|
nix run nixpkgs#silver-searcher -- -G '\.nix$' -0l 'description.*"[Aa]n?' pkgs \
| xargs -0 nix run nixpkgs#gnused -- -i '' -Ee 's/(description.*")[Aa]n? (.)/\1\U\2/'
|
|
The nixpkgs-unstable channel's programs.sqlite was used to identify
packages producing exactly one binary, and these automatically added
to their package definitions wherever possible.
|
|
meson 1.1.1 -> 1.2.0 had a few breaking changes.
upstream fixed it on both the main 1.6 and legacy 1.4 branches,
but only published a release for `gupnp_1_6`: for the legacy `gupnp` we
have to cherry-pick that fix.
|
|
|
|
|
|
|
|
https://gitlab.gnome.org/GNOME/gupnp/-/compare/gupnp-1.4.3...gupnp-1.4.4
Changelog-Reviewed-By: Jan Tojnar <jtojnar@gmail.com>
|
|
https://gitlab.gnome.org/GNOME/gupnp/-/compare/gupnp-1.4.3...gupnp-1.5.3
Changelog-Reviewed-By: Jan Tojnar <jtojnar@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes CVE-2021-33516.
https://discourse.gnome.org/t/security-relevant-releases-for-gupnp-issue-cve-2021-33516/6536
|
|
Since GNOME version is now 40, it no longer makes sense to use the old attribute name.
|
|
both patches are merged upstream
meson.build changes no longer required as upstream does it too
|
|
|
|
continuation of #109595
pkgconfig was aliased in 2018, however, it remained in
all-packages.nix due to its wide usage. This cleans
up the remaining references to pkgs.pkgsconfig and
moves the entry to aliases.nix.
python3Packages.pkgconfig remained unchanged because
it's the canonical name of the upstream package
on pypi.
|
|
|
|
https://gitlab.gnome.org/GNOME/gupnp/blob/gupnp-1.2.0/NEWS
Co-Authored-By: Tor Hedin Brønner <torhedinbronner@gmail.com>
|
|
camelCase package name was a huge inconsistency in GNOME package set.
|
|
|
|
|
|
|
|
|
|
|
|
Fixed all references, hopefully.
libxml2Python is slightly hacky now, but it seems to work.
|
|
|
|
(My OCD kicked in today...)
Remove repeated package names, capitalize first word, remove trailing
periods and move overlong descriptions to longDescription.
I also simplified some descriptions as well, when they were particularly
long or technical, often based on Arch Linux' package descriptions.
I've tried to stay away from generated expressions (and I think I
succeeded).
Some specifics worth mentioning:
* cron, has "Vixie Cron" in its description. The "Vixie" part is not
mentioned anywhere else. I kept it in a parenthesis at the end of the
description.
* ctags description started with "Exuberant Ctags ...", and the
"exuberant" part is not mentioned elsewhere. Kept it in a parenthesis
at the end of description.
* nix has the description "The Nix Deployment System". Since that
doesn't really say much what it is/does (especially after removing
the package name!), I changed that to "Powerful package manager that
makes package management reliable and reproducible" (borrowed from
nixos.org).
* Tons of "GNU Foo, Foo is a [the important bits]" descriptions
is changed to just [the important bits]. If the package name doesn't
contain GNU I don't think it's needed to say it in the description
either.
|
|
|
|
|
|
|
|
|
|
Likewise for propagatedBuildNativeInputs, etc. "buildNativeInputs"
sounds like an imperative rather than a noun phrase.
|
|
Propagate some inputs
svn path=/nixpkgs/trunk/; revision=33038
|
|
svn path=/nixpkgs/trunk/; revision=22795
|
|
svn path=/nixpkgs/trunk/; revision=12149
|