1. 03 Jan, 2015 1 commit
  2. 18 Dec, 2014 1 commit
  3. 21 Nov, 2014 1 commit
  4. 19 Nov, 2014 2 commits
    • Dan Winship's avatar
      man, docs: add the secret flags notes non-hackishly · c7341c98
      Dan Winship authored
      Since libnm-core secret-flags properties are now enum-typed rather
      than just being uints, we can now actually recognize them when
      generating docs, rather than just assuming that every property whose
      name ends in '-flags', but isn't in NMSettingDcb, is a secret-flags
      property.
      c7341c98
    • Dan Winship's avatar
      libnm, libnm-util: move settings doc generation to libnm-core · c1448698
      Dan Winship authored
      Move the settings/plugins doc generation from libnm-util to
      libnm-core, since libnm-util isn't being updated for all new
      properties.
      
      With this commit, the keyfile and ifcfg-rh documentation is basically
      unchanged, except that deprecated properties are now gone, and new
      properties have been added, and the sections are in a different order.
      (generate-plugin-docs.pl just outputs the settings in Makefile order,
      and they were unsorted in libnm-util, but are sorted in libnm-core).
      
      The settings documentation used for nm-settings.5, the D-Bus API docs,
      and the nmcli help is changed a bit more at this point, and mostly for
      the worse, since the libnm-core setting properties don't match up with
      the D-Bus API as well as the libnm-util ones do. To be fixed...
      
      (I also removed the "plugins docs" line in each plugin docs comment
      block while moving them, since those blocks will be used for more than
      just plugins soon, and it's sort of obvious anyway.)
      c1448698
  5. 14 Nov, 2014 1 commit
    • Dan Winship's avatar
      docs: make the settings docs work from tarball builds · 16a9fc49
      Dan Winship authored
      docs/api/settings-spec.xml was accidentally not getting disted,
      because gtk-doc.make explicitly removes all DISTCLEANFILES from
      distdir. However, it doesn't actually make sense for the settings docs
      files to be in DISTCLEANFILES anyway; they were put there rather than
      CLEANFILES (IIRC) so that "make clean" in a tarball build wouldn't
      delete them and break things. But the right fix is to just make them
      only be in CLEANFILES when BUILD_SETTING_DOCS is true, and not ever
      get deleted otherwise.
      
      Also adjust the build rules to ensure that the generated docs don't
      get rebuilt in tarball builds, since that can cause problems when
      building from a read-only source tree, etc.
      
      Meanwhile, in an unrelated but also fatal bug, configure.ac's check
      for if the generated docs were already present never got updated for
      the cli/src -> clients/cli move, and so even if we had been disting
      settings-spec.xml, configure would still think that the tarball didn't
      have all of the generated docs in it, so SETTING_DOCS_AVAILABLE would
      be set false and none of the generated docs would get used.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=740035
      16a9fc49
  6. 07 Nov, 2014 5 commits
  7. 31 Oct, 2014 2 commits
  8. 28 Oct, 2014 1 commit
    • Dan Winship's avatar
      libnm: rename NMVpnPlugin to NMVpnPluginOld · f4526060
      Dan Winship authored
      Rename libnm's NMVpnPlugin to NMVpnPluginOld, in preparation for
      having a new-and-improved NMVpnPlugin in NM 1.2. Also remove it from
      NM-1.0.gir.
      
      Make nm-vpn-plugin-old.h be separately includable, since it's not
      included from NetworkManager.h, and we probably don't want it to be.
      
      Remove NMVpnPlugin, NMVpnPluginUiInterface, and nm-vpn-plugin-utils
      from the docs, since they're basically undocumented anyway.
      f4526060
  9. 10 Oct, 2014 1 commit
  10. 18 Sep, 2014 3 commits
    • Dan Winship's avatar
      libnm: port to GDBus · 6793a32a
      Dan Winship authored
      Port libnm-core/libnm to GDBus.
      
      The NetworkManager daemon continues to use dbus-glib; the
      previously-added connection hash/variant conversion methods are now
      moved to NetworkManagerUtils (along with a few other utilities that
      are now only needed by the daemon code).
      6793a32a
    • Dan Winship's avatar
      libnm-core: change connection hash tables to variants in API · acf86f68
      Dan Winship authored
      In preparation for porting to GDBus, make nm_connection_to_dbus(),
      etc, represent connections as GVariants of type 'a{sa{sv}}' rather
      than as GHashTables-of-GHashTables-of-GValues.
      
      This means we're constantly converting back and forth internally, but
      this is just a stepping stone on the way to the full GDBus port, and
      all of that code will go away again later.
      acf86f68
    • Dan Winship's avatar
      libnm: merge libnm-vpn into libnm · 280b1e50
      Dan Winship authored
      There's not much point in keeping them separate: all existing
      libnm-glib-vpn users also link against libnm-glib, and the amount of
      extra code added to libnm by merging in libnm-vpn is negligible.
      
      Additionally, nm-vpn-plugin will later need access to some
      libnm-internal APIs.
      
      So, merge them together.
      280b1e50
  11. 04 Sep, 2014 1 commit
    • Dan Winship's avatar
      libnm: fix NMIP4Config/NMIP6Config addresses/routes properties · 98959d54
      Dan Winship authored
      The docs for NMIP4Config:addresses and NMIP4Config:routes claimed that
      they were GPtrArrays of NMIP4Address/NMIP4Route, but get_property()
      was actually trying to set them the D-Bus representation type, and it
      was failing anyway because it used g_value_set_boxed() on a parameter
      that was declared GParamSpecPointer. Fix it to use a GPtrArray-valued
      property, and set it to the right thing.
      
      NMIP6Config did the right thing with its :addresses and :routes
      properties, but was using custom types (NM_TYPE_IP6_ADDRESS_OBJECT_ARRAY and
      NM_TYPE_IP6_ROUTE_OBJECT_ARRAY). Make it use G_TYPE_PTR_ARRAY instead.
      
      nm-types.c, nm-types.h, and nm-types-private.h are now empty, and so
      can be dropped.
      98959d54
  12. 22 Aug, 2014 1 commit
    • Thomas Haller's avatar
      all: add nm-core-internal.h header · ef32da01
      Thomas Haller authored
      Add a header file to expose private utility functions from libnm-core
      that can be used by NetworkManager (core) and libnm.so. The header
      is also used to give privileged access to libnm-core. Since NM links
      statically, these functions are not exported and not part of public ABI.
      
      This also removes the NM_UTILS_PRIVATE_CALL() macro and libnm.so no
      longer exports nm_utils_get_private().
      
      Before, this functionality was partly declared in nm-utils-private.h.
      This was wrong because nm-utils-private.h is for functionality
      entirely private to libnm-core.
      Signed-off-by: Thomas Haller's avatarThomas Haller <thaller@redhat.com>
      ef32da01
  13. 01 Aug, 2014 1 commit
  14. 15 Jul, 2014 1 commit
  15. 01 Jul, 2014 1 commit
  16. 27 Jun, 2014 1 commit
  17. 19 Jun, 2014 1 commit
  18. 13 May, 2014 1 commit
  19. 13 Feb, 2014 1 commit
    • Dan Winship's avatar
      libnm-util, libnm-glib: add versioned deprecation/availability macros · 9c4d86ee
      Dan Winship authored
      Add versioned NM_DEPRECATED_IN_* and NM_AVAILABLE_IN_* macros, and tag
      new/deprecated functions accordingly. (All currently-deprecated
      functions are assumed to have been deprecated in 0.9.10.)
      
      Add NM_VERSION_MIN_REQUIRED and NM_VERSION_MAX_ALLOWED macros which
      can be set to determine which versions will cause warnings.
      
      With the current settings, external consumers of the
      libnm-util/libnm-glib APIs will have MIN_REQUIRED and MAX_ALLOWED both
      set to NM_VERSION_0_9_8 by default, meaning they will get warnings
      about functions added in 0.9.10. NM internally sets
      NM_VERSION_MAX_ALLOWED to NM_VERSION_NEXT_STABLE to ensure that it is
      always allowed to use all APIs.
      9c4d86ee
  20. 17 Dec, 2013 1 commit
  21. 07 Nov, 2013 1 commit
  22. 31 Oct, 2013 1 commit
  23. 19 Oct, 2013 1 commit
  24. 29 Aug, 2013 1 commit
  25. 14 May, 2013 1 commit
  26. 12 Feb, 2013 1 commit
    • Jiří Klimeš's avatar
      build: fix build with --enable-doc (docs/api/Makefile.am) · 76b5e24a
      Jiří Klimeš authored
      "./autogen.sh --enable-doc && make" produced this error:
      warning: failed to load external entity "../settings-spec.xml"
      ../network-manager-docs.xml:57: element include: XInclude error : could not load ../settings-spec.xml, and no fallback was found
      
      Removing settings-spec.xml from $(content_files) made the file non-DISTed but it
      also removed the file as a dependency for html-build.stamp that also runs
      cd html && gtkdoc-mkhtml $$mkhtml_options $(MKHTML_OPTIONS) $(DOC_MODULE) ../$(DOC_MAIN_SGML_FILE)
      and $(DOC_MAIN_SGML_FILE) includes settings-spec.xml.
      
      Fix that by making $(DOC_MAIN_SGML_FILE) dependent on setting-spec.xml.
      76b5e24a
  27. 05 Feb, 2013 3 commits
  28. 15 Jan, 2013 1 commit
  29. 30 Nov, 2012 2 commits