libgeda: Correct ld version number.

Closes-bug: lp-1081799
libgeda: Fix errors in hu.po

Closes-bug: lp-1081594

(imported from commit 4cfce9a6cda682f8093a261a6bf65bf35e6799f7)
Various manpage fixes

 * Fix typo in gxyrs manpage
 * Fix whatis entry in gmk_sym manpage
 * Fix hyphens

Closes-bug: lp-1081303

(imported from commit 2db16cd536b95ffb98721946aa36984f8a41d896)
gschem: Update copyright date in usage & 'About' dialog.
Update NEWS.
Update translations.
Update version numbers to 1.8.1.
libgeda: Refuse to connect nets inside symbols with other nets.

A libgeda crash bug was caused by the pathological use case of putting
nets inside symbols.  Since the file format does not specifically
forbid this, libgeda must cope with this gracefully.  Specifically,
o_net_consolidate() was causing a crash when attempting to merge a net
inside a symbol and a normal net.  The underlying cause was found to
be that the connection tracking system did not cope properly with
encountering connectable objects other than pins inside symbols.
Merely fixing the net consolidation algorithm exposed other bugs (for
example, nets inside symbols should NOT rubberband!)

This patch adds logic to s_conn_update_line_object() as follows:

1) If two objects are both not inside symbols, they may connect.

2) If two objects are inside the same complex, they may connect.

3) If an object is inside a complex, it must be a pin to connect to
   objects outside the complex.

Closes-bug: lp-994361

(imported from commit c18a0826fcd43dc8471f98e3a092d3144fcb6918)
gnetlist: Safer use of nettattrib-generated refdes.

Two-pronged attack to make gnetlist's use of autogenerated "POWER"
refdes less likely to cause a problem.

1) Use a longer, more specific prefix string.  This will make it much
   much less likely that a collision with a user net name will occur.

2) When testing for autogenerated refdes, test for the exact prefix
   using strncmp() instead of just checking that it appears somewhere
   in the string.

Affects-bug: lp-1226246
gnetlist: Error on clashes with netattrib-generated refdes.

Exit with an error if a refdes is found in input files that conflicts
with autogenerated netattrib-related refdes.

Closes-bug: lp-1226246
gschem: Breakout selection manipulation into a separate class

Allows multiple non-modal dialog boxes to be updated when objects in
the selection change.
gschem: Breakout gschem toplevel into a separate include
gschem: Create a free function for the gschem toplevel
Use GtkComboBoxEntry for GTK less than 2.24

Signed-off-by: Edward Hennessy <ehennes@sbcglobal.net>
Update README with new Automake requirement.
build-sys: Only expand AM_PROG_AR if defined.

Recent versions of Automake warn if AM_PROG_AR is not expanded befor
AC_PROG_LIBTOOL.  Unfortunately, AM_PROG_AR is only defined in
Automake >= 1.12.0.

Since we're only including AM_PROG_AR in order to shut Automake's
warnings up, only expand it if it's actually defined.

Closes-bug: lp-1229074
gnetlist: Don't use gettext macros.

Commit dcd9b1c6eb47 introduced a translatable string to gnetlist, but
in the stable-1.8 branch gnetlist is not yet internationalised.
build-sys: Require Automake 1.11 for developers.

A newer version of Automake is required in order to ensure that the
parallel test driver is available.

In newer versions of Automake, this new driver is used by default and
it's necessary to use

  AM_INIT_AUTOMAKE([serial-tests])

in order to get the (deprecated!) serial test driver currently used
throughout the geda-gaf package.  This doesn't provide a solution: at
the moment, we have the problem that 1) newer versions of Automake
choke on the test suite without the "serial-tests" option; 2) older
versions of Automake choke on the "serial-tests" option.

The only option available to retain the ability for all
currently-active developers to run the test suite is to port it to the
parallel test driver.  1.6.0 is too old; 1.11.0 was released in 2009
and seems to provide a reasonable balance between maturity, widespread
availability and features.  Note that users without Automake >= 1.11.0
will still be able to build tarballs, but will need to upgrade to
build from git.

(imported from commit 0dd51a48d23c2f45ce1040fceadf653dbba008e7)
build-sys: Ignore new build-tools installed by Automake 1.13.

(imported from commit 4d5db45a89ad35b37fcb894b27801f953ce28e94)
build-sys: Use GUILE_PKG_NAME instead of GUILE_PKG.

We previously stored the name of Guile's pkg-config module in a
variable called GUILE_PKG.  In recent releases of Guile 2.x, a
GUILE_PKG autoconf macro has been added which conflicts with this.  So
we need to use a different variable name instead.

(imported from commit 1c2f215ffa639f543a0ca1997c17cfbeffb76793)