cafkafk/nixpkgs
cafkafk/nixpkgs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2
nixpkgs/pkgs/tools/networking/network-manager/default.nix

127 lines
4.5 KiB
Nix
Raw Normal View History

network-manager: fix paths
2018-12-22 00:58:48 +01:00
{ stdenv, fetchurl, substituteAll, intltool, pkgconfig, dbus, dbus-glib
networkmanager: port to Meson All hail Meson! One serious issue is that building docs does not work. We patch gobject-introspection to use absolute paths for shared libraries in GIR files. Building the NetworkManager docs relies on the produced introspection data but since the library is not yet installed at the time the docs are generated, the build will fail. It works in Autotools for some reason; they probably use the pregenerated GIRs from the tarball. Disabling the docs completely is not possible at the moment either, since nmc [depends on them][1]. I have decided to fix this by pointing the installed location to the one in the build directory using libredirect. Unfortunately, we cannot just set the environment variables directly, since the build system runs the documentation generator in a clean environment. I have also added man, doc and devdoc outputs so the generated files have somewhere to go. Secondly, since Nix store is immutable, we also cannot use the package prefix for configuration and mutable state data. At the same time, we cannot write to the appropriate global directories during build. Autotools allowed to change this in installFlags but Meson lacks similar mechanism so we need to patch the build files. Finally, I also removed the at_console patch since the permission has been removed in 0.9.10. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=796755
2019-04-20 05:26:57 +02:00
, gnome3, systemd, libuuid, polkit, gnutls, ppp, dhcp, iptables, python3, vala
, libgcrypt, dnsmasq, bluez5, readline, libselinux, audit
gobject-introspection: rename package camelCase package name was a huge inconsistency in GNOME package set.
2018-12-02 12:41:15 +01:00
, gobject-introspection, modemmanager, openresolv, libndp, newt, libsoup
treewide: remove unused variables (#63177) * treewide: remove unused variables * making ofborg happy
2019-06-16 21:59:06 +02:00
, ethtool, gnused, iputils, kmod, jansson, gtk-doc, libxslt
networkmanager: port to Meson All hail Meson! One serious issue is that building docs does not work. We patch gobject-introspection to use absolute paths for shared libraries in GIR files. Building the NetworkManager docs relies on the produced introspection data but since the library is not yet installed at the time the docs are generated, the build will fail. It works in Autotools for some reason; they probably use the pregenerated GIRs from the tarball. Disabling the docs completely is not possible at the moment either, since nmc [depends on them][1]. I have decided to fix this by pointing the installed location to the one in the build directory using libredirect. Unfortunately, we cannot just set the environment variables directly, since the build system runs the documentation generator in a clean environment. I have also added man, doc and devdoc outputs so the generated files have somewhere to go. Secondly, since Nix store is immutable, we also cannot use the package prefix for configuration and mutable state data. At the same time, we cannot write to the appropriate global directories during build. Autotools allowed to change this in installFlags but Meson lacks similar mechanism so we need to patch the build files. Finally, I also removed the at_console patch since the permission has been removed in 0.9.10. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=796755
2019-04-20 05:26:57 +02:00
, docbook_xsl, docbook_xml_dtd_412, docbook_xml_dtd_42, docbook_xml_dtd_43
treewide: remove unused variables (#63177) * treewide: remove unused variables * making ofborg happy
2019-06-16 21:59:06 +02:00
, openconnect, curl, meson, ninja, libpsl }:
network-manager: packaged, maybe even works. svn path=/nixpkgs/trunk/; revision=25367
2011-01-03 19:01:10 +01:00
networkmanager: add updateScript
2018-03-07 06:09:48 +01:00
let
networkmanager: 1.10.6 → 1.12.0
2018-07-05 22:30:53 +02:00
pname = "NetworkManager";
networkmanager: port to Meson All hail Meson! One serious issue is that building docs does not work. We patch gobject-introspection to use absolute paths for shared libraries in GIR files. Building the NetworkManager docs relies on the produced introspection data but since the library is not yet installed at the time the docs are generated, the build will fail. It works in Autotools for some reason; they probably use the pregenerated GIRs from the tarball. Disabling the docs completely is not possible at the moment either, since nmc [depends on them][1]. I have decided to fix this by pointing the installed location to the one in the build directory using libredirect. Unfortunately, we cannot just set the environment variables directly, since the build system runs the documentation generator in a clean environment. I have also added man, doc and devdoc outputs so the generated files have somewhere to go. Secondly, since Nix store is immutable, we also cannot use the package prefix for configuration and mutable state data. At the same time, we cannot write to the appropriate global directories during build. Autotools allowed to change this in installFlags but Meson lacks similar mechanism so we need to patch the build files. Finally, I also removed the at_console patch since the permission has been removed in 0.9.10. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=796755
2019-04-20 05:26:57 +02:00
pythonForDocs = python3.withPackages (pkgs: with pkgs; [ pygobject3 ]);
networkmanager: add updateScript
2018-03-07 06:09:48 +01:00
in stdenv.mkDerivation rec {
networkmanager: 1.10.6 → 1.12.0
2018-07-05 22:30:53 +02:00
name = "network-manager-${version}";
networkmanager: 1.18.1 -> 1.18.2 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/1.18.2/NEWS
2019-07-31 08:54:59 +02:00
version = "1.18.2";
network-manager: packaged, maybe even works. svn path=/nixpkgs/trunk/; revision=25367
2011-01-03 19:01:10 +01:00
src = fetchurl {
networkmanager: 1.10.6 → 1.12.0
2018-07-05 22:30:53 +02:00
url = "mirror://gnome/sources/${pname}/${stdenv.lib.versions.majorMinor version}/${pname}-${version}.tar.xz";
networkmanager: 1.18.1 -> 1.18.2 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/1.18.2/NEWS
2019-07-31 08:54:59 +02:00
sha256 = "1hx5dx5dgdqh3p8fq7q1pxy2bx2iymc74lj60ycrf7ydfjlprnad";
network-manager: packaged, maybe even works. svn path=/nixpkgs/trunk/; revision=25367
2011-01-03 19:01:10 +01:00
};
networkmanager: port to Meson All hail Meson! One serious issue is that building docs does not work. We patch gobject-introspection to use absolute paths for shared libraries in GIR files. Building the NetworkManager docs relies on the produced introspection data but since the library is not yet installed at the time the docs are generated, the build will fail. It works in Autotools for some reason; they probably use the pregenerated GIRs from the tarball. Disabling the docs completely is not possible at the moment either, since nmc [depends on them][1]. I have decided to fix this by pointing the installed location to the one in the build directory using libredirect. Unfortunately, we cannot just set the environment variables directly, since the build system runs the documentation generator in a clean environment. I have also added man, doc and devdoc outputs so the generated files have somewhere to go. Secondly, since Nix store is immutable, we also cannot use the package prefix for configuration and mutable state data. At the same time, we cannot write to the appropriate global directories during build. Autotools allowed to change this in installFlags but Meson lacks similar mechanism so we need to patch the build files. Finally, I also removed the at_console patch since the permission has been removed in 0.9.10. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=796755
2019-04-20 05:26:57 +02:00
outputs = [ "out" "dev" "devdoc" "man" "doc" ];
networkmanager: Update to 0.9.4.0
2012-06-16 21:09:30 +02:00
Trying to fix networkmanager svn path=/nixpkgs/trunk/; revision=29160
2011-09-10 21:23:26 +02:00
# Right now we hardcode quite a few paths at build time. Probably we should
# patch networkmanager to allow passing these path in config file. This will
# remove unneeded build-time dependencies.
networkmanager: port to Meson All hail Meson! One serious issue is that building docs does not work. We patch gobject-introspection to use absolute paths for shared libraries in GIR files. Building the NetworkManager docs relies on the produced introspection data but since the library is not yet installed at the time the docs are generated, the build will fail. It works in Autotools for some reason; they probably use the pregenerated GIRs from the tarball. Disabling the docs completely is not possible at the moment either, since nmc [depends on them][1]. I have decided to fix this by pointing the installed location to the one in the build directory using libredirect. Unfortunately, we cannot just set the environment variables directly, since the build system runs the documentation generator in a clean environment. I have also added man, doc and devdoc outputs so the generated files have somewhere to go. Secondly, since Nix store is immutable, we also cannot use the package prefix for configuration and mutable state data. At the same time, we cannot write to the appropriate global directories during build. Autotools allowed to change this in installFlags but Meson lacks similar mechanism so we need to patch the build files. Finally, I also removed the at_console patch since the permission has been removed in 0.9.10. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=796755
2019-04-20 05:26:57 +02:00
mesonFlags = [
"-Ddhclient=${dhcp}/bin/dhclient"
"-Ddnsmasq=${dnsmasq}/bin/dnsmasq"
Trying to fix networkmanager svn path=/nixpkgs/trunk/; revision=29160
2011-09-10 21:23:26 +02:00
# Upstream prefers dhclient, so don't add dhcpcd to the closure
networkmanager: port to Meson All hail Meson! One serious issue is that building docs does not work. We patch gobject-introspection to use absolute paths for shared libraries in GIR files. Building the NetworkManager docs relies on the produced introspection data but since the library is not yet installed at the time the docs are generated, the build will fail. It works in Autotools for some reason; they probably use the pregenerated GIRs from the tarball. Disabling the docs completely is not possible at the moment either, since nmc [depends on them][1]. I have decided to fix this by pointing the installed location to the one in the build directory using libredirect. Unfortunately, we cannot just set the environment variables directly, since the build system runs the documentation generator in a clean environment. I have also added man, doc and devdoc outputs so the generated files have somewhere to go. Secondly, since Nix store is immutable, we also cannot use the package prefix for configuration and mutable state data. At the same time, we cannot write to the appropriate global directories during build. Autotools allowed to change this in installFlags but Meson lacks similar mechanism so we need to patch the build files. Finally, I also removed the at_console patch since the permission has been removed in 0.9.10. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=796755
2019-04-20 05:26:57 +02:00
"-Ddhcpcd=no"
networkmanager: disable dhcpcanon instead of assuming in /usr/*
2019-04-27 02:22:16 +02:00
"-Ddhcpcanon=no"
networkmanager: port to Meson All hail Meson! One serious issue is that building docs does not work. We patch gobject-introspection to use absolute paths for shared libraries in GIR files. Building the NetworkManager docs relies on the produced introspection data but since the library is not yet installed at the time the docs are generated, the build will fail. It works in Autotools for some reason; they probably use the pregenerated GIRs from the tarball. Disabling the docs completely is not possible at the moment either, since nmc [depends on them][1]. I have decided to fix this by pointing the installed location to the one in the build directory using libredirect. Unfortunately, we cannot just set the environment variables directly, since the build system runs the documentation generator in a clean environment. I have also added man, doc and devdoc outputs so the generated files have somewhere to go. Secondly, since Nix store is immutable, we also cannot use the package prefix for configuration and mutable state data. At the same time, we cannot write to the appropriate global directories during build. Autotools allowed to change this in installFlags but Meson lacks similar mechanism so we need to patch the build files. Finally, I also removed the at_console patch since the permission has been removed in 0.9.10. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=796755
2019-04-20 05:26:57 +02:00
"-Dpppd=${ppp}/bin/pppd"
"-Diptables=${iptables}/bin/iptables"
networkmanager: cleanup using more placeholder
2018-12-22 21:22:20 +01:00
# to enable link-local connections
networkmanager: port to Meson All hail Meson! One serious issue is that building docs does not work. We patch gobject-introspection to use absolute paths for shared libraries in GIR files. Building the NetworkManager docs relies on the produced introspection data but since the library is not yet installed at the time the docs are generated, the build will fail. It works in Autotools for some reason; they probably use the pregenerated GIRs from the tarball. Disabling the docs completely is not possible at the moment either, since nmc [depends on them][1]. I have decided to fix this by pointing the installed location to the one in the build directory using libredirect. Unfortunately, we cannot just set the environment variables directly, since the build system runs the documentation generator in a clean environment. I have also added man, doc and devdoc outputs so the generated files have somewhere to go. Secondly, since Nix store is immutable, we also cannot use the package prefix for configuration and mutable state data. At the same time, we cannot write to the appropriate global directories during build. Autotools allowed to change this in installFlags but Meson lacks similar mechanism so we need to patch the build files. Finally, I also removed the at_console patch since the permission has been removed in 0.9.10. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=796755
2019-04-20 05:26:57 +02:00
"-Dudev_dir=${placeholder "out"}/lib/udev"
"-Dresolvconf=${openresolv}/bin/resolvconf"
"-Ddbus_conf_dir=${placeholder "out"}/etc/dbus-1/system.d"
"-Dsystemdsystemunitdir=${placeholder "out"}/etc/systemd/system"
"-Dkernel_firmware_dir=/run/current-system/firmware"
"--sysconfdir=/etc"
"--localstatedir=/var"
"-Dcrypto=gnutls"
"-Dsession_tracking=systemd"
"-Dmodem_manager=true"
"-Dnmtui=true"
"-Ddocs=true"
networkmanager: 1.16.0 -> 1.18.0 * build w/iwd support since it's free (no dep required!) * move to iputils for minor utilities, instead of inetutils * parallel building :) https://gitlab.freedesktop.org/NetworkManager/NetworkManager/raw/1.18.0/NEWS
2019-04-23 05:12:53 +02:00
# TODO: legacy library, will be *removed* in next release!
"-Dlibnm_glib=true"
networkmanager: port to Meson All hail Meson! One serious issue is that building docs does not work. We patch gobject-introspection to use absolute paths for shared libraries in GIR files. Building the NetworkManager docs relies on the produced introspection data but since the library is not yet installed at the time the docs are generated, the build will fail. It works in Autotools for some reason; they probably use the pregenerated GIRs from the tarball. Disabling the docs completely is not possible at the moment either, since nmc [depends on them][1]. I have decided to fix this by pointing the installed location to the one in the build directory using libredirect. Unfortunately, we cannot just set the environment variables directly, since the build system runs the documentation generator in a clean environment. I have also added man, doc and devdoc outputs so the generated files have somewhere to go. Secondly, since Nix store is immutable, we also cannot use the package prefix for configuration and mutable state data. At the same time, we cannot write to the appropriate global directories during build. Autotools allowed to change this in installFlags but Meson lacks similar mechanism so we need to patch the build files. Finally, I also removed the at_console patch since the permission has been removed in 0.9.10. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=796755
2019-04-20 05:26:57 +02:00
"-Dtests=no"
"-Dqt=false"
networkmanager: 1.16.0 -> 1.18.0 * build w/iwd support since it's free (no dep required!) * move to iputils for minor utilities, instead of inetutils * parallel building :) https://gitlab.freedesktop.org/NetworkManager/NetworkManager/raw/1.18.0/NEWS
2019-04-23 05:12:53 +02:00
# Allow using iwd when configured to do so
"-Diwd=true"
networkmanager: libaudit yes but disabled by default
2019-04-27 02:53:27 +02:00
"-Dlibaudit=yes-disabled-by-default"
networkmanager: Build with ModemManager support
2014-02-13 18:03:06 +01:00
];
Trying to fix networkmanager svn path=/nixpkgs/trunk/; revision=29160
2011-09-10 21:23:26 +02:00
network-manager: 1.4.4 -> 1.6.4
2017-04-04 14:16:59 +02:00
patches = [
networkmanager: 1.10.6 → 1.12.0
2018-07-05 22:30:53 +02:00
(substituteAll {
src = ./fix-paths.patch;
networkmanager: sed from gnused, not coreutils! fix bad path
2019-05-04 02:19:49 +02:00
inherit iputils kmod openconnect ethtool gnused dbus;
network-manager: fix paths
2018-12-22 00:58:48 +01:00
inherit (stdenv) shell;
networkmanager: 1.10.6 → 1.12.0
2018-07-05 22:30:53 +02:00
})
networkmanager: port to Meson All hail Meson! One serious issue is that building docs does not work. We patch gobject-introspection to use absolute paths for shared libraries in GIR files. Building the NetworkManager docs relies on the produced introspection data but since the library is not yet installed at the time the docs are generated, the build will fail. It works in Autotools for some reason; they probably use the pregenerated GIRs from the tarball. Disabling the docs completely is not possible at the moment either, since nmc [depends on them][1]. I have decided to fix this by pointing the installed location to the one in the build directory using libredirect. Unfortunately, we cannot just set the environment variables directly, since the build system runs the documentation generator in a clean environment. I have also added man, doc and devdoc outputs so the generated files have somewhere to go. Secondly, since Nix store is immutable, we also cannot use the package prefix for configuration and mutable state data. At the same time, we cannot write to the appropriate global directories during build. Autotools allowed to change this in installFlags but Meson lacks similar mechanism so we need to patch the build files. Finally, I also removed the at_console patch since the permission has been removed in 0.9.10. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=796755
2019-04-20 05:26:57 +02:00
# Meson does not support using different directories during build and
# for installation like Autotools did with flags passed to make install.
./fix-install-paths.patch
network-manager: 1.4.4 -> 1.6.4
2017-04-04 14:16:59 +02:00
];
network-manager: give path to pppd executable This fixes an issue I have faced when trying to connect to the internet via wwan gsm modem. (cherry picked from commit 0775adc599f4706e3ff020e700b5f8f69578b6b1) Closes https://github.com/NixOS/nixpkgs/pull/19812
2016-10-16 20:29:18 +02:00
networkmanager: 1.10.6 → 1.12.0
2018-07-05 22:30:53 +02:00
buildInputs = [
networkmanager: port to Meson All hail Meson! One serious issue is that building docs does not work. We patch gobject-introspection to use absolute paths for shared libraries in GIR files. Building the NetworkManager docs relies on the produced introspection data but since the library is not yet installed at the time the docs are generated, the build will fail. It works in Autotools for some reason; they probably use the pregenerated GIRs from the tarball. Disabling the docs completely is not possible at the moment either, since nmc [depends on them][1]. I have decided to fix this by pointing the installed location to the one in the build directory using libredirect. Unfortunately, we cannot just set the environment variables directly, since the build system runs the documentation generator in a clean environment. I have also added man, doc and devdoc outputs so the generated files have somewhere to go. Secondly, since Nix store is immutable, we also cannot use the package prefix for configuration and mutable state data. At the same time, we cannot write to the appropriate global directories during build. Autotools allowed to change this in installFlags but Meson lacks similar mechanism so we need to patch the build files. Finally, I also removed the at_console patch since the permission has been removed in 0.9.10. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=796755
2019-04-20 05:26:57 +02:00
systemd libselinux audit libpsl libuuid polkit ppp libndp curl
gobject-introspection: rename package camelCase package name was a huge inconsistency in GNOME package set.
2018-12-02 12:41:15 +01:00
bluez5 dnsmasq gobject-introspection modemmanager readline newt libsoup jansson
networkmanager: 1.10.6 → 1.12.0
2018-07-05 22:30:53 +02:00
];
Trying to fix networkmanager svn path=/nixpkgs/trunk/; revision=29160
2011-09-10 21:23:26 +02:00
networkmanager: port to Meson All hail Meson! One serious issue is that building docs does not work. We patch gobject-introspection to use absolute paths for shared libraries in GIR files. Building the NetworkManager docs relies on the produced introspection data but since the library is not yet installed at the time the docs are generated, the build will fail. It works in Autotools for some reason; they probably use the pregenerated GIRs from the tarball. Disabling the docs completely is not possible at the moment either, since nmc [depends on them][1]. I have decided to fix this by pointing the installed location to the one in the build directory using libredirect. Unfortunately, we cannot just set the environment variables directly, since the build system runs the documentation generator in a clean environment. I have also added man, doc and devdoc outputs so the generated files have somewhere to go. Secondly, since Nix store is immutable, we also cannot use the package prefix for configuration and mutable state data. At the same time, we cannot write to the appropriate global directories during build. Autotools allowed to change this in installFlags but Meson lacks similar mechanism so we need to patch the build files. Finally, I also removed the at_console patch since the permission has been removed in 0.9.10. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=796755
2019-04-20 05:26:57 +02:00
propagatedBuildInputs = [ dbus-glib gnutls libgcrypt ];
Better propagated/native/ buildInputs separation svn path=/nixpkgs/trunk/; revision=29270
2011-09-14 17:50:01 +02:00
networkmanager: port to Meson All hail Meson! One serious issue is that building docs does not work. We patch gobject-introspection to use absolute paths for shared libraries in GIR files. Building the NetworkManager docs relies on the produced introspection data but since the library is not yet installed at the time the docs are generated, the build will fail. It works in Autotools for some reason; they probably use the pregenerated GIRs from the tarball. Disabling the docs completely is not possible at the moment either, since nmc [depends on them][1]. I have decided to fix this by pointing the installed location to the one in the build directory using libredirect. Unfortunately, we cannot just set the environment variables directly, since the build system runs the documentation generator in a clean environment. I have also added man, doc and devdoc outputs so the generated files have somewhere to go. Secondly, since Nix store is immutable, we also cannot use the package prefix for configuration and mutable state data. At the same time, we cannot write to the appropriate global directories during build. Autotools allowed to change this in installFlags but Meson lacks similar mechanism so we need to patch the build files. Finally, I also removed the at_console patch since the permission has been removed in 0.9.10. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=796755
2019-04-20 05:26:57 +02:00
nativeBuildInputs = [
meson ninja intltool pkgconfig
vala gobject-introspection
dbus-glib # for dbus-binding-tool
# Docs
gtk-doc libxslt docbook_xsl docbook_xml_dtd_412 docbook_xml_dtd_42 docbook_xml_dtd_43 pythonForDocs
];
NM: propagate dbus-glib svn path=/nixpkgs/trunk/; revision=29247
2011-09-13 21:27:41 +02:00
tree-wide: disable `doCheck` and `doInstallCheck` where it fails (the trivial part)
2018-04-25 05:20:18 +02:00
doCheck = false; # requires /sys, the net
networkmanager: 1.16.0 -> 1.18.0 * build w/iwd support since it's free (no dep required!) * move to iputils for minor utilities, instead of inetutils * parallel building :) https://gitlab.freedesktop.org/NetworkManager/NetworkManager/raw/1.18.0/NEWS
2019-04-23 05:12:53 +02:00
networkmanager: port to Meson All hail Meson! One serious issue is that building docs does not work. We patch gobject-introspection to use absolute paths for shared libraries in GIR files. Building the NetworkManager docs relies on the produced introspection data but since the library is not yet installed at the time the docs are generated, the build will fail. It works in Autotools for some reason; they probably use the pregenerated GIRs from the tarball. Disabling the docs completely is not possible at the moment either, since nmc [depends on them][1]. I have decided to fix this by pointing the installed location to the one in the build directory using libredirect. Unfortunately, we cannot just set the environment variables directly, since the build system runs the documentation generator in a clean environment. I have also added man, doc and devdoc outputs so the generated files have somewhere to go. Secondly, since Nix store is immutable, we also cannot use the package prefix for configuration and mutable state data. At the same time, we cannot write to the appropriate global directories during build. Autotools allowed to change this in installFlags but Meson lacks similar mechanism so we need to patch the build files. Finally, I also removed the at_console patch since the permission has been removed in 0.9.10. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=796755
2019-04-20 05:26:57 +02:00
postPatch = ''
patchShebangs ./tools
patchShebangs libnm/generate-setting-docs.py
networkmanager: Stop using libredirect for building docs Our gobject-introspection patches make the shared library paths absolute in the GIR files. When building docs, the library is not yet installed, though, so we need to replace the absolute path with a local one during build. Previously we used LD_PRELOAD to load libredirect and rewrite the installed paths to ones in the build directory. That was unnecessary complicated and many people spent whole night trying to figure out why it breaks some programs. Using a symlink from the installed location to the build directory fixes the issue as well, while having much less moving parts, thus being easier to grasp. The symlink will be overridden during installation.
2019-05-04 05:47:04 +02:00
'';
NetworkManager: Fix aliases and dependencies There are two fixes in this commit. Firstly, I am creating proper symlinks for the Alias= definitions in the .service files. This achieves the same result as `systemctl enable`, and I think is preferred over `mv`. Secondly, `networkmanager-init` now wants `NetworkManager.service`, along with `ModemManager.service`. ModemManager does not depend on NetworkManager (according to `systemctl list-dependencies ModemManager`), thus NetworkManager never got started on boot.
2014-02-12 12:29:18 +01:00
networkmanager: Stop using libredirect for building docs Our gobject-introspection patches make the shared library paths absolute in the GIR files. When building docs, the library is not yet installed, though, so we need to replace the absolute path with a local one during build. Previously we used LD_PRELOAD to load libredirect and rewrite the installed paths to ones in the build directory. That was unnecessary complicated and many people spent whole night trying to figure out why it breaks some programs. Using a symlink from the installed location to the build directory fixes the issue as well, while having much less moving parts, thus being easier to grasp. The symlink will be overridden during installation.
2019-05-04 05:47:04 +02:00
preBuild = ''
# Our gobject-introspection patches make the shared library paths absolute
# in the GIR files. When building docs, the library is not yet installed,
# though, so we need to replace the absolute path with a local one during build.
# We are using a symlink that will be overridden during installation.
mkdir -p ${placeholder "out"}/lib
ln -s $PWD/libnm/libnm.so.0 ${placeholder "out"}/lib/libnm.so.0
networkmanager: port to Meson All hail Meson! One serious issue is that building docs does not work. We patch gobject-introspection to use absolute paths for shared libraries in GIR files. Building the NetworkManager docs relies on the produced introspection data but since the library is not yet installed at the time the docs are generated, the build will fail. It works in Autotools for some reason; they probably use the pregenerated GIRs from the tarball. Disabling the docs completely is not possible at the moment either, since nmc [depends on them][1]. I have decided to fix this by pointing the installed location to the one in the build directory using libredirect. Unfortunately, we cannot just set the environment variables directly, since the build system runs the documentation generator in a clean environment. I have also added man, doc and devdoc outputs so the generated files have somewhere to go. Secondly, since Nix store is immutable, we also cannot use the package prefix for configuration and mutable state data. At the same time, we cannot write to the appropriate global directories during build. Autotools allowed to change this in installFlags but Meson lacks similar mechanism so we need to patch the build files. Finally, I also removed the at_console patch since the permission has been removed in 0.9.10. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=796755
2019-04-20 05:26:57 +02:00
'';
network-manager: Rename dispatcher service Rename NetworkManager-dispatcher.service to dbus-org.freedesktop.nm-dispatcher.service so it is found by systemd (NixOS doesn't handle the Alias directive in the unit file)
2013-10-03 14:45:25 +02:00
networkmanager: port to Meson All hail Meson! One serious issue is that building docs does not work. We patch gobject-introspection to use absolute paths for shared libraries in GIR files. Building the NetworkManager docs relies on the produced introspection data but since the library is not yet installed at the time the docs are generated, the build will fail. It works in Autotools for some reason; they probably use the pregenerated GIRs from the tarball. Disabling the docs completely is not possible at the moment either, since nmc [depends on them][1]. I have decided to fix this by pointing the installed location to the one in the build directory using libredirect. Unfortunately, we cannot just set the environment variables directly, since the build system runs the documentation generator in a clean environment. I have also added man, doc and devdoc outputs so the generated files have somewhere to go. Secondly, since Nix store is immutable, we also cannot use the package prefix for configuration and mutable state data. At the same time, we cannot write to the appropriate global directories during build. Autotools allowed to change this in installFlags but Meson lacks similar mechanism so we need to patch the build files. Finally, I also removed the at_console patch since the permission has been removed in 0.9.10. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=796755
2019-04-20 05:26:57 +02:00
postInstall = ''
network-manager: 1.0.12 -> 1.2.2
2016-06-22 02:40:18 +02:00
# systemd in NixOS doesn't use `systemctl enable`, so we need to establish
# aliases ourselves.
ln -s $out/etc/systemd/system/NetworkManager-dispatcher.service $out/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service
network-manager: rename systemd service back to match upstream Compatibility with other distributions/software and expectation of users coming from other systems should have higher priority over consistency. In particular this fixes #51375, where the NetworkManager-wait-online.service broke as a result of this.
2018-12-02 13:11:44 +01:00
ln -s $out/etc/systemd/system/NetworkManager.service $out/etc/systemd/system/dbus-org.freedesktop.NetworkManager.service
network-manager: add legacy service name as fallback This prevents NetworkManager from not starting back up while switching configurations. This can be removed once 19.10 is released.
2019-03-19 01:54:27 +01:00
# Add the legacy service name from before #51382 to prevent NetworkManager
# from not starting back up:
# TODO: remove this once 19.10 is released
ln -s $out/etc/systemd/system/NetworkManager.service $out/etc/systemd/system/network-manager.service
network-manager: 1.0.12 -> 1.2.2
2016-06-22 02:40:18 +02:00
'';
networkmanager: Update to 0.9.4.0
2012-06-16 21:09:30 +02:00
networkmanager: add updateScript
2018-03-07 06:09:48 +01:00
passthru = {
updateScript = gnome3.updateScript {
packageName = pname;
attrPath = "networkmanager";
};
};
network-manager: packaged, maybe even works. svn path=/nixpkgs/trunk/; revision=25367
2011-01-03 19:01:10 +01:00
meta = with stdenv.lib; {
networkmanager: 1.10.6 → 1.12.0
2018-07-05 22:30:53 +02:00
homepage = https://wiki.gnome.org/Projects/NetworkManager;
network-manager: Fix building against systemd http://hydra.nixos.org/build/3473319
2012-12-12 16:26:03 +01:00
description = "Network configuration and management tool";
networkmanager: 1.10.6 → 1.12.0
2018-07-05 22:30:53 +02:00
license = licenses.gpl2Plus;
treewide: purge maintainers.urkud It's sad, but he's been inactive for the last five years. Keeping such people in meta.maintainers is counter-productive.
2017-03-27 19:11:17 +02:00
maintainers = with maintainers; [ phreedom rickynils domenkozar obadz ];
networkmanager: 1.10.6 → 1.12.0
2018-07-05 22:30:53 +02:00
platforms = platforms.linux;
network-manager: packaged, maybe even works. svn path=/nixpkgs/trunk/; revision=25367
2011-01-03 19:01:10 +01:00
};
network-manager: use mirror://gnome svn path=/nixpkgs/trunk/; revision=25371
2011-01-03 20:10:01 +01:00
}
Reference in a new issue Copy permalink