Commit 6024897f authored by Jeremy Bicha's avatar Jeremy Bicha

New upstream version 3.8.1

parents 6d24be79 489f3e7e
German Poo-Caaman~o <gpoo@ubiobio.cl>
William Jon McCann <mccann@jhu.edu>
Carlos Garcia Campos <carlosgc@gnome.org>
Rodrigo Moya <rodrigo@gnome-db.org>
This diff is collapsed.
This diff is collapsed.
Installation Instructions
*************************
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
Software Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
Basic Installation
==================
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You only need
`configure.ac' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that the
`configure' script does not know about. Run `./configure --help' for
details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory. After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.
Installation Names
==================
By default, `make install' installs the package's commands under
`/usr/local/bin', include files under `/usr/local/include', etc. You
can specify an installation prefix other than `/usr/local' by giving
`configure' the option `--prefix=PREFIX'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
pass the option `--exec-prefix=PREFIX' to `configure', the package uses
PREFIX as the prefix for installing programs and libraries.
Documentation and other data files still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' cannot figure out automatically,
but needs to determine by the type of machine the package will run on.
Usually, assuming the package is built to be run on the _same_
architectures, `configure' can figure that out, but if it prints a
message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
CPU-COMPANY-SYSTEM
where SYSTEM can have one of these forms:
OS KERNEL-OS
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the option `--target=TYPE' to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share, you
can create a site shell script called `config.site' that gives default
values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Defining Variables
==================
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
causes the specified `gcc' to be used as the C compiler (unless it is
overridden in the site shell script). Here is a another example:
/bin/bash ./configure CONFIG_SHELL=/bin/bash
Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
configuration-related scripts to be executed by `/bin/bash'.
`configure' Invocation
======================
`configure' recognizes the following options to control how it operates.
`--help'
`-h'
Print a summary of the options to `configure', and exit.
`--version'
`-V'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`--cache-file=FILE'
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
`--config-cache'
`-C'
Alias for `--cache-file=config.cache'.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.
ACLOCAL_AMFLAGS = -I m4 ${ACLOCAL_FLAGS}
SUBDIRS = pixmaps data src help po
EXTRA_DIST = \
intltool-extract.in \
intltool-merge.in \
intltool-update.in \
mkinstalldirs
DISTCLEANFILES = \
intltool-extract \
intltool-merge \
intltool-update
This diff is collapsed.
This diff is collapsed.
gnome-nettool: GNOME interface for various networking tools
GNOME Nettool is a set of front-ends to various networking command-line
tools, like ping, netstat, ifconfig, whois, traceroute, finger.
Bug fixes:
[X] Add any new entry at the end of GtkTreeView, not in the cursor
position. This bug is valid on ping, traceroute and scan.
General:
[ ] Add gconf support to store:
- Last host requested
- Last settings used (count ping, netstat query, etc)
[ ] Implement information of network devices
[X] Add support for IPv6
[ ] To implement "link state" and "collission"
[X] Implement traceroute (with tcp and/or icmp)
[X] Implement netstat
[X] Add DNS query
[X] Add Whois query
[X] Add support to IPv6 (ping6, traceroute6, network interface)
[ ] Add Copy-to-clipboard on Information (info.c)
[X] Show error messages, feeback to the user.
(for instance: Host not found)
[ ] Glib-ize util-mii
i18n:
[X] Add internacionalization support (mostly add files in POTFILES.in)
UI:
[ ] A graphical traceroute
[X] A better ping output: GtkTreeView instead GtkTextView and
a label to show the perfomance every time.
[ ] Accept arguments by command line.
Portability:
[-] Multiplataform support (may be with a ping/traceroute helper to
process de same output)
[X] Detection of network devices
[X] Add *BSD support in ping command/output
This diff is collapsed.
This diff is collapsed.
/* config.h.in. Generated from configure.ac by autoheader. */
/* always defined to indicate that i18n is enabled */
#undef ENABLE_NLS
/* The gettext package */
#undef GETTEXT_PACKAGE
/* Define to 1 if you have the `bind_textdomain_codeset' function. */
#undef HAVE_BIND_TEXTDOMAIN_CODESET
/* Define to 1 if you have the `dcgettext' function. */
#undef HAVE_DCGETTEXT
/* Define to 1 if you have the <dlfcn.h> header file. */
#undef HAVE_DLFCN_H
/* Define if the GNU gettext() function is already present or preinstalled. */
#undef HAVE_GETTEXT
/* Define to 1 if you have the <ifaddrs.h> header file. */
#undef HAVE_IFADDRS_H
/* Define to 1 if you have the <inttypes.h> header file. */
#undef HAVE_INTTYPES_H
/* Define if your <locale.h> file defines LC_MESSAGES. */
#undef HAVE_LC_MESSAGES
/* Define to 1 if you have the <locale.h> header file. */
#undef HAVE_LOCALE_H
/* Define to 1 if you have the <memory.h> header file. */
#undef HAVE_MEMORY_H
/* Define to 1 if you have the <stdint.h> header file. */
#undef HAVE_STDINT_H
/* Define to 1 if you have the <stdlib.h> header file. */
#undef HAVE_STDLIB_H
/* Define to 1 if you have the <strings.h> header file. */
#undef HAVE_STRINGS_H
/* Define to 1 if you have the <string.h> header file. */
#undef HAVE_STRING_H
/* Define to 1 if you have the <sys/socket.h> header file. */
#undef HAVE_SYS_SOCKET_H
/* Define to 1 if you have the <sys/sockio.h> header file. */
#undef HAVE_SYS_SOCKIO_H
/* Define to 1 if you have the <sys/stat.h> header file. */
#undef HAVE_SYS_STAT_H
/* Define to 1 if you have the <sys/types.h> header file. */
#undef HAVE_SYS_TYPES_H
/* Define to 1 if you have the <unistd.h> header file. */
#undef HAVE_UNISTD_H
/* Define to the sub-directory in which libtool stores uninstalled libraries.
*/
#undef LT_OBJDIR
/* Name of package */
#undef PACKAGE
/* Define to the address where bug reports for this package should be sent. */
#undef PACKAGE_BUGREPORT
/* Define to the full name of this package. */
#undef PACKAGE_NAME
/* Define to the full name and version of this package. */
#undef PACKAGE_STRING
/* Define to the one symbol short name of this package. */
#undef PACKAGE_TARNAME
/* Define to the home page for this package. */
#undef PACKAGE_URL
/* Define to the version of this package. */
#undef PACKAGE_VERSION
/* Define to 1 if you have the ANSI C header files. */
#undef STDC_HEADERS
/* Version number of package */
#undef VERSION
This diff is collapsed.
This diff is collapsed.
AC_PREREQ([2.64])
AC_INIT([GNOME Nettool],
[3.8.1],
[http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-nettool],
[gnome-nettool],
[http://projects.gnome.org/gnome-network/]) #FIXME: website should be updated, it is even yet named gnome-network
AC_CONFIG_HEADERS([config.h])
AC_CONFIG_SRCDIR([src/ping.c])
AC_CONFIG_MACRO_DIR([m4])
AM_INIT_AUTOMAKE([1.11.1 foreign])
AM_MAINTAINER_MODE([enable])
# Support silent build rules, requires at least automake-1.11. Disable
# by either passing --disable-silent-rules to configure or passing V=1
# to make
AM_SILENT_RULES([yes])
# Check for programs
AC_PROG_CC
# Initialize libtool
LT_PREREQ([2.2])
LT_INIT
# Check headers
AC_CHECK_HEADERS(sys/sockio.h)
AC_CHECK_HEADERS(sys/socket.h ifaddrs.h,,AC_MSG_ERROR(Required header not found: $ac_header))
dnl ******************************************
dnl ** pkg-config dependacy checks **
dnl ******************************************
GIO_REQUIRED=2.26.0
GTK_REQUIRED=3.0.0
PKG_CHECK_MODULES(NETTOOL,
gtk+-3.0 >= $GTK_REQUIRED
gio-2.0 >= $GIO_REQUIRED
gmodule-export-2.0
libgtop-2.0)
AC_SUBST(NETTOOL_CFLAGS)
AC_SUBST(NETTOOL_LIBS)
dnl
dnl Translations
dnl
IT_PROG_INTLTOOL([0.40.0])
GETTEXT_PACKAGE=gnome-nettool
AC_SUBST(GETTEXT_PACKAGE)
AC_DEFINE_UNQUOTED(GETTEXT_PACKAGE,"$GETTEXT_PACKAGE",[The gettext package])
AM_GLIB_GNU_GETTEXT
#User Documentation
YELP_HELP_INIT
dnl
dnl GSettings stuff
dnl
GLIB_GSETTINGS
dnl
dnl Debugging flags
dnl
GNOME_COMPILE_WARNINGS([maximum])
CFLAGS="$CFLAGS $WARN_CFLAGS"
set_debug=no
AC_ARG_ENABLE(debug,
[ --enable-debug Lots of noisy debug messages],
set_debug="$enableval")
AC_MSG_CHECKING(if debug messages are enabled)
if test "$set_debug" != "no"; then
AC_MSG_RESULT(yes)
CFLAGS="-DGRD_DEBUG $CFLAGS"
else
AC_MSG_RESULT(no)
fi
AC_SUBST(CFLAGS)
AC_SUBST(CPPFLAGS)
AC_SUBST(LDFLAGS)
AC_CONFIG_FILES([
Makefile
data/Makefile
data/gnome-nettool.desktop.in
help/Makefile
pixmaps/Makefile
pixmaps/icons/Makefile
pixmaps/icons/16x16/Makefile
pixmaps/icons/16x16/apps/Makefile
pixmaps/icons/22x22/Makefile
pixmaps/icons/22x22/apps/Makefile
pixmaps/icons/24x24/Makefile
pixmaps/icons/24x24/apps/Makefile
pixmaps/icons/32x32/Makefile
pixmaps/icons/32x32/apps/Makefile
pixmaps/icons/scalable/Makefile
pixmaps/icons/scalable/apps/Makefile
po/Makefile.in
src/Makefile])
AC_OUTPUT
uidir = $(pkgdatadir)/ui
ui_DATA = gnome-nettool.ui
gsettings_SCHEMAS = org.gnome.gnome-nettool.gschema.xml
@INTLTOOL_XML_NOMERGE_RULE@
@GSETTINGS_RULES@
desktopdir = $(datadir)/applications
desktop_in_in_files = gnome-nettool.desktop.in.in
desktop_in_files = $(desktop_in_in_files:.desktop.in.in=.desktop.in)
desktop_DATA = $(desktop_in_files:.desktop.in=.desktop)
@INTLTOOL_DESKTOP_RULE@
EXTRA_DIST = \
$(desktop_in_in_files) \
org.gnome.gnome-nettool.gschema.xml.in \
$(ui_DATA)
DISTCLEANFILES = \
$(desktop_in_files) \
$(gsettings_SCHEMAS)
CLEANFILES = \
$(desktop_DATA)
This diff is collapsed.
[Desktop Entry]
_Name=Network Tools
_Comment=View information about your network
_Keywords=network;monitor;remote;
Exec=gnome-nettool
Icon=gnome-nettool
Terminal=false
Type=Application
Categories=System;Utility;GNOME;GTK;
StartupNotify=true
X-GNOME-Bugzilla-Bugzilla=GNOME
X-GNOME-Bugzilla-Product=gnome-nettool
X-GNOME-Bugzilla-Component=general
X-GNOME-Bugzilla-Version=@PACKAGE_VERSION@
This diff is collapsed.
<?xml version="1.0" encoding="UTF-8"?>
<schemalist>
<schema path="/org/gnome/gnome-nettool/" id="org.gnome.gnome-nettool" gettext-domain="gnome-nettool">
<key type="as" name="hostnames">
<default>[]</default>
<_summary>Historically used hostnames</_summary>
<_description>A list of hostnames previously used</_description>
</key>
<key type="as" name="usernames">
<default>[]</default>
<_summary>Historically used usernames</_summary>
<_description>A list of usernames previously used</_description>
</key>
<key type="as" name="domains">
<default>[]</default>
<_summary>Historically used domains</_summary>
<_description>A list of domains previously used</_description>
</key>
</schema>
</schemalist>
This diff is collapsed.
<page xmlns="http://projectmallard.org/1.0/"
type="guide" style="task"
id="index">
<info>
<title type='link' role="trail"><media type="image" src="figures/gnome-nettool-trail.png"/></title>
<title type='link'>Net Tool</title>
<title type='text'>Net Tool</title>
<revision pkgversion="3.2" version="0.1" date="2012-10-01" status="stub"/>
<credit type="author">
<name>Germán Poo-Caamaño</name>
<email>gpoo@gnome.org</email>
<years>2012</years>
</credit>
<desc>A network diagnostic tool</desc>
<license>
<p>Creative Commons Share Alike 3.0</p>
</license>
</info>
<title><media type="image" src="figures/gnome-nettool.png">Net Tool logo</media>Net Tool</title>
<section id="information" style="2column">
<title>Getting Network Information</title>
</section>
</page>
<page xmlns="http://projectmallard.org/1.0/"
type="topic" style="task"
id="introduction">
<info>
<link type="guide" xref="index"/>
<desc>Introduction to the <em>Net Tool</em>.</desc>
<revision pkgversion="3.2" version="0.1" date="2012-10-01" status="stub"/>
<credit type="author">
<name>Germán Poo-Caamaño</name>
<email>gpoo@gnome.org</email>
<years>2012</years>
</credit>
<license>
<p>Creative Commons Share Alike 3.0</p>
</license>
</info>
<title>Introduction</title>
<p>
<app>Nettool</app> is a tool to diagnose the network and services status.
It provides a graphical user interface for a number of common network
tools, such as ping, netstat, traceroute, port scan, lookup, finger,
and whois.
</p><p>