| Commit message (Collapse) | Author | Age |
|---|
| |\ |
|
| | |\
| | |
| | | |
lib.meta: introduce `availableOn` to check package availability on given platform
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ /
| |
| |
| | |
This reverts commit 420f89ceb267b461eed5d025b6c3c0e57703cc5c.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since 03eaa48 added perl.withPackages, there is a canonical way to
create a perl interpreter from a list of libraries, for use in script
shebangs or generic build inputs. This method is declarative (what we
are doing is clear), produces short shebangs[1] and needs not to wrap
existing scripts.
Unfortunately there are a few exceptions that I've found:
1. Scripts that are calling perl with the -T switch. This makes perl
ignore PERL5LIB, which is what perl.withPackages is using to inform
the interpreter of the library paths.
2. Perl packages that depends on libraries in their own path. This
is not possible because perl.withPackages works at build time. The
workaround is to add `-I $out/${perl.libPrefix}` to the shebang.
In all other cases I propose to switch to perl.withPackages.
[1]: https://lwn.net/Articles/779997/
|
| |
|
|
| |
Signed-off-by: Ben Siraphob <bensiraphob@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This reverts commit c778945806b44d46ec16bc4302e7e7163e6bab97.
I believe this is exactly what brings the staging branch into
the right shape after the last merge from master (through staging-next);
otherwise part of staging changes would be lost
(due to being already reachable from master but reverted).
|
| |
|
|
|
|
|
| |
I'm sorry; I didn't notice it contained staging commits.
This reverts commit 17f5305b6c20df795c365368d2d868266519599e, reversing
changes made to a8a018ddc0a8b5c3d4fa94c94b672c37356bc075.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit fb6d63f3fdd95a5468d43a0693c8ca7c1894363f.
I really hope this finally fixes #99236: evaluation on Hydra.
This time I really did check basically the same commit on Hydra:
https://hydra.nixos.org/eval/1618011
Right now I don't have energy to find what exactly is wrong in the
commit, and it doesn't seem important in comparison to nixos-unstable
channel being stuck on a commit over one week old.
|
| | |
|
| |
|
|
| |
Signed-off-by: Sascha Grunert <sgrunert@suse.com>
|
| |
|
|
| |
This reverts commit 4b028aecae881fbfbe51, as planned.
|
| |
|
|
|
| |
This is to avoid the huge rebuild for now, as it seems to be enough to
fix the problem, but I'll revert this on staging anyway.
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| | |
Co-Authored-By: Drew <drewrisinger@users.noreply.github.com>
|
| | |
| |
| |
| |
| |
| | |
Ran the same script as #78265.
Additionally, manually replaced `http://goodies.xfce.org`
with https.
|
| |/
|
|
| |
drop patches that were merged upstream
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This sort of code breaks config.{allowBroken, allowUnsupportedSystem} =
true by making them do unpredictable things.
|
| |
|
|
|
|
|
| |
I *want* cross-specific overrides to be verbose, so I rather not have
this shorthand. This makes the syntactic overhead more proportional to
the maintainence cost. Hopefully this pushes people towards fewer
conditionals and more abstractions.
|
| |
|
|
| |
trivial part)
|
| | |
|
| |
|
|
| |
(update: drop patches no longer needed on updated version)
|
| |
|
|
|
|
|
|
| |
* apparmor: updating utilities to fresh python
* apparmor: better way to depend on python
* apparmor: override python derivation on the top-level
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This prevents systemd and by extension a zillion other packages from
having Python 2.7 in their closure. For example, the closure of
systemd dropped from 133 MiB to 85 MiB.
|
| |
|
|
|
|
| |
- Move build tools to nativeBuildInputs
- capability.h should come from linuxHeaders not glibc
- Delete v2.9
|
| | |
|
| |\
| |
| |
| | |
Many non-conflict problems weren't (fully) resolved in this commit yet.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows all utilties to at least run, though most still fail
because they expect to be able to read a non-existent config file.
Also, aa-notify refuses to run due to a self-check on the filename,
which cannot be preceded by a '.'. This has to be patched or we
need to set PERL5LIB some other way.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
An incremental release, including several fixes to the parser, library, and
userspace management tools. See [1] for a comprehensive changelog.
[1]: http://wiki.apparmor.net/index.php/ReleaseNotes_2_10
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This was untested and didn't function without a dbus patch which wasn't
applied to the system dbus package, so it wasn't used at all.
Also, it creates a weird cyclic dependency if we want systemd to depend
on libapparmor (for AppArmorProfiles= support), because libapparmor then
wants dbus, and dbus wants systemd. Oof.
Luckily, this feature and whatnot will probably all be irrelevant in the
glorious kdbus-based future, and the dbus patches aren't even upstream I
think. So we can just drop it.
Signed-off-by: Austin Seipp <aseipp@pobox.com>
|