summaryrefslogtreecommitdiff
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
* build: check for reallocarray in stdlib.hLeo2020-12-101-0/+1
|
* release: bump version to 1.29.5 (development)1.29.5-devThomas Haller2020-12-061-2/+2
|\
| * release: bump version to 1.29.4 (development)1.29.4-devThomas Haller2020-12-031-1/+1
| |
| * release: bump version to 1.29.3 (development)1.29.3-devBeniamino Galvani2020-11-271-1/+1
| |
| * release: bump version to 1.29.2 (development)1.29.2-devBeniamino Galvani2020-11-181-1/+1
| |
| * release: bump version to 1.29.1 (development)1.29.1-devAntonio Cardace2020-11-021-1/+1
| |
| * release: bump version to 1.29.0 (development)1.29.0-devBeniamino Galvani2020-10-051-2/+2
| |
* | release: bump version to 1.28.01.28.0Thomas Haller2020-12-061-2/+2
| |
* | release: bump version to 1.27.91 (1.28-rc2) (development)1.28-rc2Beniamino Galvani2020-10-201-1/+1
|/
* release: bump version to 1.27.90 (1.28-rc1)1.28-rc1Beniamino Galvani2020-10-051-1/+1
|
* release: bump version to 1.27.3 (development)1.27.3-devBeniamino Galvani2020-09-141-1/+1
|
* release: bump version to 1.27.2 (development)1.27.2-devThomas Haller2020-09-021-1/+1
|
* dns: add new "rc-manager=auto" modeThomas Haller2020-08-241-10/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a new `main.rc-manager=auto` setting, that favours to use systemd-resolved (and not touch "/etc/resolv.conf" but configure it via D-Bus), or falls back to `resolvconf`/`netconfig` binaries if they are installed and enabled at compile time. As final fallback use "symlink", like before. Note that on Fedora there is no "openresolv" package ([1]). Instead, "systemd" package provides "/usr/sbin/resolvconf" as a wrapper for systemd-resolved's "resolvectl". On such a system the fallback to resolvconf is always wrong, because NetworkManager should either talk to systemd-resolved directly or not but never call "/usr/sbin/resolvconf". So, the special handling for resolvconf and netconfig is only done if NetworkManager was build with these applications explicitly enabled. Note that SUSE builds NetworkManager with --with-netconfig=yes --with-config-dns-rc-manager-default=netconfig and the new option won't be used there either. But of course, netconfig already does all the right things on SUSE. [1] https://bugzilla.redhat.com/show_bug.cgi?id=668153 Suggested-by: Jason A. Donenfeld <Jason@zx2c4.com>
* build: prefer python3 over python2 in autotools's configure scriptThomas Haller2020-08-171-1/+4
| | | | | | On Debian sid, pygobject no longer builds "python-gobject" for python2. Still, python2 may be installed and detected preferably by AM_PATH_PYTHON(). Add workaround.
* release: bump version to 1.27.1 (development)1.27.1-devThomas Haller2020-07-131-21/+12
|\
| * all: bump libjansson dependency to 2.7Thomas Haller2020-07-091-1/+1
| | | | | | | | | | | | | | | | | | jansson 2.7 was released October 2014. It's also in Ubuntu 16.06. Other distros (like CentOS 7.5 and Debian Stretch/9) have both newer versions. Bump the requirement, simply because our CI does not use such old version so it's not clear whether it works at all.
| * libnm: always build libnm with JSON validationThomas Haller2020-07-091-16/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We anyway load libjansson with dlopen(), and already before it could happen that libjansson is not available. In that case, we would not crash, but simply proceed without json validation. Since libnm-core no longer uses libjansson directly, but only via "nm-glib-aux/nm-json.h", we can just always compile with that, and use it at runtime. That means, libjansson is not a build dependency for libnm anymore, so we don't need a compile time check. Note that if you build without libjansson, then JANSSON_SONAME is undefined, and loading it will still fail at runtime. So, even if we now always build with all our code enabled, it only works if you actually build with libjansson. Still, it's simpler to drop the conditional build, as the only benefit is a (minimally) smaller build.
| * all: fix typo in man pagesSayed Shah2020-07-031-2/+2
| | | | | | | | | | | | | | | | There should be a comma after 'Otherwise' and 'Currently'. https://bugzilla.redhat.com/show_bug.cgi?id=1852452 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/560
| * build: create check for python blackSayed Shah2020-06-191-0/+4
| | | | | | | | | | | | | | If python black is install then it would check the formating of all of the python files and test the for it. Otherwise, it would just simply ignore the python black if python black is not installed.
| * build: fix detecting use of pregenerated docs in "configure.ac"Thomas Haller2020-06-161-2/+3
| | | | | | | | | | | | Without it, we fail to use the pregenerated gtk-doc files. Fixes: 8a78b15c9b29 ('docs: merge branch 'th/nm-settings-manual'')
| * release: bump version to 1.27.0 (development)1.27.0-devThomas Haller2020-06-151-2/+2
| |
* | release: bump version to 1.26.01.26.0Thomas Haller2020-07-131-2/+2
| |
* | release: bump version to 1.25.91 (1.26-rc2) (development)1.26-rc2Thomas Haller2020-06-281-1/+1
| |
* | build: fix detecting use of pregenerated docs in "configure.ac"Thomas Haller2020-06-161-2/+3
|/ | | | | | | Without it, we fail to use the pregenerated gtk-doc files. Fixes: 8a78b15c9b29 ('docs: merge branch 'th/nm-settings-manual'') (cherry picked from commit 56b15ca0b615a12e06df0e56a921b575c26a0019)
* release: bump version to 1.25.90 (1.26-rc1)1.26-rc1Thomas Haller2020-06-151-1/+1
|
* docs: add more nm-settings manpages (dbus,nmcli,keyfile,ifcfg-rh)Thomas Haller2020-06-111-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | A significant part of NetworkManager's API are the connection profiles, documented in `man nm-settings*`. But there are different aspects about profiles, depending on what you are interested. There is the D-Bus API, nmcli options, keyfile format, and ifcfg-rh format. Additionally, there is also libnm API. Add distinct manual pages for the four aspects. Currently the two new manual pages "nm-settings-dbus" and "nm-settings-nmcli" are still identical to the former "nm-settings.5" manual. In the future, they will diverge to account for the differences. There are the following aspects: - "dbus" - "keyfile" - "ifcfg-rh" - "nmcli" For "libnm" we don't generate a separate "nm-settings-libnm" manual page. That is instead documented via gtk-doc. Currently the keyfile and ifcfg-rh manual pages only detail settings which differ. But later I think also these manual pages should contain all settings that apply.
* release: bump version to 1.25.2-dev1.25.2-devBeniamino Galvani2020-05-291-1/+1
|
* build: log system-ca-path configure setting in build scriptsThomas Haller2020-05-271-0/+1
|
* build: install a firewalld zone for shared modeBeniamino Galvani2020-05-151-0/+13
| | | | | | | Install a NM-specific firewalld zone to be used for interfaces that are used for connection sharing. The zone blocks all traffic to the local machine except some protocols (DHCP, DNS and ICMP) and allows all forwarded traffic.
* build/autotools: reject invalid sanitizer options in configure.acThomas Haller2020-05-141-0/+8
|
* release: bump version to 1.25.1-dev after 1.25.0 release1.25.1-devThomas Haller2020-05-081-2/+2
|\
| * build: remove subshells and fix invalid test syntaxGilles Dartiguelongue2020-04-201-26/+26
| | | | | | | | | | | | Signed-off-by: Gilles Dartiguelongue <eva@gentoo.org> https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/472
| * release: bump version to 1.25.0 (development)1.25.0-devBeniamino Galvani2020-04-101-2/+2
| |
* | release: bump version to 1.24.01.24.0Thomas Haller2020-05-081-2/+2
| |
* | release: bump version to 1.23.91 (1.24-rc2)1.24-rc2Thomas Haller2020-05-021-1/+1
| |
* | build: remove subshells and fix invalid test syntaxGilles Dartiguelongue2020-04-201-26/+26
|/ | | | | | | Signed-off-by: Gilles Dartiguelongue <eva@gentoo.org> https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/472 (cherry picked from commit e073491b9ce0bfd77d3c7e818fdd442a696726a9)
* release: bump version to 1.23.90 (1.24-rc1)1.24-rc1Beniamino Galvani2020-04-101-1/+1
|
* release: bump version to 1.23.2-dev1.23.2-devThomas Haller2020-02-211-1/+1
|
* autotools: define the polkit-agent package prefix when building without ↵Antonio Cardace2019-12-241-2/+4
| | | | | | polkit-devel Fixes: df1d214b2 (clients: polkit-agent: implement polkit agent without using libpolkit)
* clients: polkit-agent: implement polkit agent without using libpolkitAntonio Cardace2019-12-241-12/+6
|
* release: bump version to 1.23.1-dev after 1.22.0 release1.23.1-devThomas Haller2019-12-171-2/+29
|\ | | | | | | | | | | | | | | | | | | After 1.22.0 is released, merge it back into master so that 1.22.0 is part of the history of master. That means, $ git log --first-parent master will also traverse 1.22.0 and 1.22-rc*. Also bump the micro version to 1.23.1-dev to indicate that this is after 1.22.0 is out.
| * systemd: merge branch systemd into masterThomas Haller2019-12-161-0/+27
| |\
| * | core: add main.auth-polkit option "root-only"Thomas Haller2019-12-111-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We always build with PolicyKit support enabled, because it has no additional dependencies, beside some D-Bus calls. However, in NetworkManager.conf the user could configure "main.auth-polkit" to disable PolicyKit. However, previously it would only allow to disable PolicyKit while granting access to all users. I think it's useful to have an option that disables PolicyKit and grants access only to root. I think we should not go too far in implementing our own authorization mechanisms beside PolicyKit (e.g. you cannot disable PolicyKit and grant access based on group membership of the user). However, disabling PolicyKit can be useful sometimes, and it's simple to implement a "root-only" setup. Note one change is that when NetworkManager now runs without a D-Bus connection (in initrd), it would deny all non-root requests. Previously it would grant access. I think there should be little difference in practice, because if we have no D-Bus we also don't have any requests to authenticate.
| * | cloud-setup: add comment that the tool is still experimentalThomas Haller2019-12-021-1/+1
| | |
| * | release: bump version to 1.23.0 (development)1.23.0-devThomas Haller2019-11-291-2/+2
| | |
* | | release: bump version to 1.22.01.22.0Thomas Haller2019-12-171-2/+2
| | |
* | | core: add main.auth-polkit option "root-only"Thomas Haller2019-12-111-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We always build with PolicyKit support enabled, because it has no additional dependencies, beside some D-Bus calls. However, in NetworkManager.conf the user could configure "main.auth-polkit" to disable PolicyKit. However, previously it would only allow to disable PolicyKit while granting access to all users. I think it's useful to have an option that disables PolicyKit and grants access only to root. I think we should not go too far in implementing our own authorization mechanisms beside PolicyKit (e.g. you cannot disable PolicyKit and grant access based on group membership of the user). However, disabling PolicyKit can be useful sometimes, and it's simple to implement a "root-only" setup. Note one change is that when NetworkManager now runs without a D-Bus connection (in initrd), it would deny all non-root requests. Previously it would grant access. I think there should be little difference in practice, because if we have no D-Bus we also don't have any requests to authenticate. (cherry picked from commit 6d7446e52f5bfe379c2b1f54f9244b33fd236e32)
* | | cloud-setup: add comment that the tool is still experimentalThomas Haller2019-12-021-1/+1
|/ / | | | | | | (cherry picked from commit 16223cff9172e8b1ea7974af4d613406b0f56607)
* | release: bump version to 1.21.90 (1.22-rc1)1.22-rc1Thomas Haller2019-11-291-1/+1
| |
* | cloud-setup: add tool for automatic IP configuration in cloudThomas Haller2019-11-281-0/+12
|/ | | | | | | | | | | | | | | | | | | | | | | | This is a tool for automatically configuring networking in a cloud environment. Currently it only supports IPv4 on EC2, but it's intended for extending to other cloud providers (Azure). See [1] and [2] for how to configure secondary IP addresses on EC2. This is what the tool currently aims to do (but in the future it might do more). [1] https://aws.amazon.com/premiumsupport/knowledge-center/ec2-ubuntu-secondary-network-interface/ It is inspired by SuSE's cloud-netconfig ([1], [2]) and ec2-net-utils package on Amazon Linux ([3], [4]). [1] https://www.suse.com/c/multi-nic-cloud-netconfig-ec2-azure/ [2] https://github.com/SUSE-Enceladus/cloud-netconfig [3] https://github.com/aws/ec2-net-utils [4] https://github.com/lorengordon/ec2-net-utils.git It is also intended to work without configuration. The main point is that you boot an image with NetworkManager and nm-cloud-setup enabled, and it just works.
View Lorry Controller Status