- Switch to using XZ-compressed tarballs
- build: Make autoconf-archive support optional
- gnome-autogen: Fix the package name tracing
- macros2: Deprecate GNOME_CXX_WARNINGS
- macros2: Deprecate GNOME_COMPILE_WARNINGS
- gnome-autogen: warn if $srcdir is undefined
- gnome-autogen: warn for deprecated variables
- gnome-autogen: infer PKG_NAME from configure.ac
- README: remove check for automake version in example
- compiler-warnings: Add -Werror=return-type
- macros2: Remove support for gnome-doc-utils
- doc-build: Remove doc-build infrastructure
- macros2: Remove GNOME_COMMON_INIT
Issues found with existing distfiles:
distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip
distfiles/fortran-utils-1.1.tar.gz
distfiles/ivykis-0.39.tar.gz
distfiles/enum-1.11.tar.gz
distfiles/pvs-3.2-libraries.tgz
distfiles/pvs-3.2-linux.tgz
distfiles/pvs-3.2-solaris.tgz
distfiles/pvs-3.2-system.tgz
No changes made to these distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
version 3.14.0
macros2: Update links to macros in the autoconf-archive
Now that the macros have been committed upstream, we can link to their
manual pages rather than the bug reports.
macros2: Add support for APPSTREAM_XML macro
And request that appstream-xml.m4 get installed if missing.
https://bugzilla.gnome.org/show_bug.cgi?id=736497
macros2: Deprecate GNOME_CODE_COVERAGE
The autoconf-archive AX_CODE_COVERAGE macro should be used instead.
https://bugzilla.gnome.org/show_bug.cgi?id=729405
macros2: Deprecate GNOME_MAINTAINER_MODE_DEFINES
The modules which it deprecates are all ancient and unused. Many of the
modules which use GNOME_MAINTAINER_MODE_DEFINES don’t make use of the
DISABLE_DEPRECATED variable it generates anyway.
If a module really wants maintainer mode, they should use
AM_MAINTAINER_MODE. Otherwise, they should just eliminate this call
entirely.
https://bugzilla.gnome.org/show_bug.cgi?id=735417
macros2: Deprecate GNOME_DEBUG_CHECK
The autoconf-archive AX_DEBUG_CHECK macro should be used instead, or the
macro contents should just be substituted into configure.ac directly,
since it’s so simple.
https://bugzilla.gnome.org/show_bug.cgi?id=729403
build: Remove a non-existent file from EXTRA_DIST
https://bugzilla.gnome.org/show_bug.cgi?id=735418
compiler-flags: allow suppressing warnings
Some projects want to see no warnings at all, for example, projects that
are written in Vala. But GNOME_COMPILE_WARNINGS([no]) is a no-op that
does nothing to turn off the default compiler warnings. Presumably if
you ask for no compiler warnings, you want no compiler warnings, so
suppress them in this case instead.
https://bugzilla.gnome.org/show_bug.cgi?id=734973
code-coverage: Support lcov 1.11
https://bugzilla.gnome.org/show_bug.cgi?id=732988
macros2: Remove FORBIDDEN_M4MACROS infrastructure
It was completely outdated and unused. The REQUIRED_M4MACROS
infrastructure is, however, still in use.
https://bugzilla.gnome.org/show_bug.cgi?id=729932
macros2: Remove outdated README file
https://bugzilla.gnome.org/show_bug.cgi?id=729410
doc: Move doc/usage.txt to README and update
We don’t like references to CVS any more. Update the guidelines to no
longer reference GNOME_COMMON_INIT.
https://bugzilla.gnome.org/show_bug.cgi?id=729410
make program_VERSION a local variable
Otherwise we may end up overriding what was manually set in the
environment.
version 3.12.0
gnome-autogen.sh: Fix check if stdin is a tty
Commit 7f977b021462 introduced a check if stdin is ins't a tty, and
prevent printing terminal codes in this case. But the check was wrong
and always failed.
https://bugzilla.gnome.org/show_bug.cgi?id=726892
gnome-autogen: require automake 1.11.2
This is the version of automake that introduced ACLOCAL_PATH support, so
make sure that we have it before attempting to configure the package.
gnome-common: use ACLOCAL_PATH over ACLOCAL_FLAGS
jhbuild has set this variable for more than two years.
https://bugzilla.gnome.org/show_bug.cgi?id=726208
gnome-autogen.sh: correct IFS value
Due to a likely copy-paste mistake, the default value of IFS was being
set to 9 spaces instead of a tab and a space. Fix that.
https://bugzilla.gnome.org/show_bug.cgi?id=726208
gnome-autogen.sh: Check for appdata-xml.m4 with APPDATA_XML
compiler-flags: Simplify a case statement slightly
compiler-flags: Replace deprecated AC_HELP_STRING with AS_HELP_STRING
Read the dirlist file unconditionally
version 3.10.0
compiler-flags: Add a #serial line
As suggested in bug #707475, this will ensure the latest version of
gnome-compiler-flags.m4 is used if conflicting versions are found in
different directories in the autoconf search path.
Helps: https://bugzilla.gnome.org/show_bug.cgi?id=707475
compiler-flags: Add an optional second argument for custom warnings
This allows module authors to choose to enforce stricter warnings on
a per-module basis, to avoid the situation where an outside
contributor submits a patch which introduces warnings the maintainer
has enabled locally.
Closes: https://bugzilla.gnome.org/show_bug.cgi?id=707475
Run intltool before autoreconf so intltool.m4 is picked up by aclocal.
https://bugzilla.gnome.org/show_bug.cgi?id=705365
gnome-autogen.sh: run glib-gettexize if using GLib gettext
This code was removed by error in
commit 323bbfe0989405725379cada1aa5cb361fd2999f
gnome-autogen.sh: Check only for autoreconf
autoconf, automake, libtool, gettext are already checked by autoreconf
Rename configure.in to configure.ac
gnome-autogen: Do not use sed to get the AC_CONFIG_MACRO_DIR directory
macros2/gnome-autogen.sh: Create m4 directory if it doesnt exits
This is a automake bug fixed in automake 1.13.2
gnome-autogen.sh: Use autoreconf
instead autopoint/libtoolize/autoconf/automake manually
Add support for automake 1.14
code-coverage: fix conditionalization
The "make clean" rule added by gnome-code-coverage.m4 was not
conditionalized (making it spew errors on "make clean" when built
without coverage support, since $(LCOV) expanded to ""), and the other
rules were conditionalized incorrectly (testing "ifdef
CODE_COVERAGE_ENABLED", when that variable was always set, just
sometimes to "no"). Fix both problems.
https://bugzilla.gnome.org/show_bug.cgi?id=699943
Add support for lcov 1.10
version 3.7.4
COPYING: add GPL-2 license file
Finally declare gnome-common to be GPL 2+, by doing some source code
archaeology.
These files we can effectively ignore:
.gitignore
AUTHORS
ChangeLog.pre-git
NEWS
README
doc-build/README
doc/usage.txt
gnome-common.doap
macros2/README.cvs-commits
The build files you could argue are boilerplate/uncopyrightable:
Makefile.am
autogen.sh
configure.in
doc-build/Makefile.am
macros2/Makefile.am
So that leaves:
doc-build/gnome-doc-common.in
doc-build/omf.make
doc-build/xmldocs.make
Appeared in e16ea58db92e05b9720acdc6992175ec346dfc91. Appears to have
been copy-pasted from scrollkeeper-example2, LGPLv2.1.
macros2/gnome-autogen.sh
Can be traced back to gnome-libs 88f7376472d3ee54329213c118b46225703d8223, which
is GPLv2/LGPLv2.
macros2/gnome-code-coverage.m4
LGPLv2.1+.
macros2/gnome-common.m4
macros2/gnome-compiler-flags.m4
Synced with gnome-core as of 425e5cc9aad003c9f64d43f2d3f15e04a97db854, so
LGPLv2.1+.
The long-standing assumption is that gnome-common was GPLv2+, so use that
license. Finally the tyranny of unclear licensing is over!
https://bugzilla.gnome.org/show_bug.cgi?id=133689
build: remove useless (empty or ancient) files that we don't need
Add support for automake 1.13.
Better support of using AUTOCONF environment variable
When I launch gnome-autogen.sh by telling it to use a version of
autoconf that is at a particular path -- by using the AUTOCONF
environment variable -- I can see that there is a spot in the script
that fails to honour that variable. I thus get the error message
(that I trim to just keep the relevant part):
AUTOCONF=/my/autoconf AUTOM4TE=/my/autom4te /bin/sh -x /usr/bin/gnome-autogen.sh
[...]
+++ find_configure_files /home/dodji/devel/git/gdl/master
+++ configure_ac=
+++ test -f /home/dodji/devel/git/gdl/master/configure.ac
+++ test -f /home/dodji/devel/git/gdl/master/configure.in
+++ configure_ac=/home/dodji/devel/git/gdl/master/configure.in
+++ test x/home/dodji/devel/git/gdl/master/configure.in '!=' x
+++ echo /home/dodji/devel/git/gdl/master/configure.in
+++ autoconf -t 'AC_CONFIG_SUBDIRS:$1' /home/dodji/devel/git/gdl/master/configure.in
+++ read dir
/home/dodji/devel/git/gdl/master/configure.in:8: error: Autoconf version 2.65 or higher is required
/home/dodji/devel/git/gdl/master/configure.in:8: the top level
autom4te: /bin/m4 failed with exit status: 63
I think the problem is that the find_configure_files function uses
'autoconf' directly instead of using $AUTOCONF. So it's taking the
autoconf binary that is in my path, and that one doesn't satisfy the
version requirement of the configure.in script template that is in.
/home/dodji/devel/git/gdl/master/configure.in.
The patch below fixes that essentially by s/autoconf/$AUTOCONF there,
and also by moving the definition point of the AUTOCONF variable --
that is done by a call to version_check -- before the first spot that
actually uses it.
It's worth noting that this bug appears to have been introduced by the
patch attached to bug #510713.
Tested on my Fedora Rawhide system.
* macros2/gnome-autogen.sh (find_configure_files): Use the
AUTOCONF variable, rather than calling the autoconf program
directly. Remove the now useless comment.
(<at global scope>): Move the definition of the AUTOCONF variable
before its first use.
compiler-warnings: Fix tabs->spaces
Per https://bugzilla.gnome.org/show_bug.cgi?id=688192
compiler-warnings: Drop -Wdeclaration-after-statement
Some GNOME modules want the ability to use C99, let's not hamper them.
https://bugzilla.gnome.org/show_bug.cgi?id=688192
compiler-warnings: Drop -Wno-sign-comare
It's not part of -Wall, and we're not explicitly turning it on here,
so there's no point in turning it off, since it's not on.
Additionally, if a given module did want it on, it's clearer if
the compiler flags don't have -Wno-sign-compare -Wsign-compare.
https://bugzilla.gnome.org/show_bug.cgi?id=688192
compiler-warnings: Move -Wnested-externs to the always-on warning set
Since there's no reason to have it different for yes/maximum.
https://bugzilla.gnome.org/show_bug.cgi?id=688192
compiler-warnings: code cleanup: Extract common warnings into variables
Will make future refactoring clearer, and also we have comments now.
https://bugzilla.gnome.org/show_bug.cgi?id=688192
compiler-warnings: Drop -Waggregate-return
This trips up gnome-desktop using things like XSyncValue, and while
it's possible to avoid, we shouldn't punish people who are pushed to
use structures as return values by external APIs.
Returning a two-element structure is not a big deal.
compiler-warnings: cosmetic cleanup: Put each warning on own line
So that further patches are more readable.
Add lots of warnings to GNOME_COMPILE_WARNINGS
Following Colin Walters' thread on desktop-devel-list:
https://mail.gnome.org/archives/desktop-devel-list/2012-July/msg00100.html
Add a selection of more strict warnings to the default level of
GNOME_COMPILE_WARNINGS. Check all the warnings by passing them to GCC,
and ignore those which fail. Set the severity of some of the warnings to
errors, so that particularly bad code is rejected (set the warning level
to ‘minimum’ is you wish to avoid this behaviour). Fixes bug 568546 and
bug 608953.
code-coverage: Relicence to LGPLv2.1+
As gnome-common is widely used, it’s useful for it to have a fairly liberal
licence. This relicences the gnome-code-coverage.m4 file from GPLv3+ to
LGPLv2.1+.
Permission has been obtained (by private e-mail) from the other contributors:
• Christian Persch <chpe@gnome.org>
• Xan Lopez <xan@gnome.org>
See also: https://bugzilla.gnome.org/show_bug.cgi?id=133689
code coverage: Quiet lcov and add extra ignore patterns
Make lcov be quiet if V=0, and add a new CODE_COVERAGE_IGNORE_PATTERN
variable to be able to add extra files to ignore in code coverage reporting.
Post release version bump
Distcheck with --disable-silent-rules
Version 2.28.0
Remove MAINTAINERS, and dist the DOAP file
Use AM_SILENT_RULES
Fix build breakage in modules caused by commit aac1a8ec
Chech for single header includes.
When maintainer mode is enabled, check for single header includes as
well as deprecated flags (#557070).
Support for automake 1.11
Remove auto-generated ChangeLog from the tree
Autogenerate ChangeLog
Trivial update
* Remove CVS references, use "repository tree"
* Fix whitespace
* Fix typo "The" -> "There"
Move to "development" category
Add the required DOAP project description (used
gnome-system-monitor as a template)
Only pass --enable-maintainer-mode when AM_MAINTAINER_MODE is present
Takeover
Revert "Add single include disabling cppflags"
Oops, this wasn't meant to be committed just yet.
This reverts commit f95de3b4b636786d1e297f40df32ee32f71ebce7.
Post branch version bump.
Add single include disabling cppflags
Default to enable maintainer mode
Add -Wno-portability to automake invocation. Bug #529120, patch by Philip Van Hoof.
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
2005-09-20 James Henstridge <james@jamesh.id.au>
* macros2/gnome-autogen.sh (configure_files): when searching for
configure.in files, skip directories starting with a dot. This
avoids Bzr, Quilt and Subversion bookkeeping directories among
others. Fixes bug #311951.
2005-08-17 Stepan Kasal <kasal@ucw.cz>
* macros2/gnome-autogen.sh (add_to_cm_macrodirs): New function,
prevents duplicates in $cm_macrodirs.
(check_m4macros): Use it. Read the dirlist file, if it is supported
by the version of Automake actually in use.
2005-08-17 Stepan Kasal <kasal@ucw.cz>
* macros2/gnome-autogen.sh (version_check): Set $variable_VERSION
to the actual version number of the tool.
2005-08-17 James Henstridge <james@jamesh.id.au>
* macros2/gnome-autogen.sh: pass --force to gnome-doc-prepare to
match other tools. Fixes bug #311775.
* macros2/gnome-autogen.sh: don't use syntax that non-GNU greps
don't understand. Fixes bug #313531.
2005-08-16 James Henstridge <james@jamesh.id.au>
* macros2/gnome-autogen.sh: add checks for gnome-common macro
names, and call require_m4macro for the appropriate names. This
can help detect $ACLOCAL_FLAGS problems earlier. Addresses bug
#312125.
2005-07-25 James Henstridge <james@jamesh.id.au>
* configure.in: bump release number.
2005-07-19 Shaun McCance <shaunm@gnome.org>
* macros2/gnome-autogen.sh:
- Bumped up the default required version of gnome-doc-utils
2005-07-18 Christian Persch <chpe@cvs.gnome.org>
* macros2/gnome-autogen.sh:
When configure.{in,ac} contains GNOME_DOC_INIT, actually call
gnome-doc-prepare.
2004-09-14 James Henstridge <james@jamesh.id.au>
* configure.in: bump version number to 2.8.0
2004-08-30 James Henstridge <james@jamesh.id.au>
* macros2/gnome-autogen.sh: fix up error message when a required
M4 file isn't found. Fixes bug #147417.
* macros2/gnome-autogen.sh: Revert Rodney's changes, since
glib-gettextize has been fixed on the HEAD and 2.4 branches.
2004-06-10 Rodney Dawes <dobey@ximian.com>
* macros2/gnome-autogen.sh: Add code to check for mkinstalldirs in
the shared automake files directory, and copy it in if we are using
AM_GLIB_GNU_GETTEXT
Fixes#144069
2004-05-26 James Henstridge <james@daa.com.au>
* macros2/gnome-compiler-warnings.m4: some small cleanups.
* macros2/gnome-common.m4 (GNOME_COMMON_INIT): since caching is
turned off in all recent Autoconfs, it doesn't make sense to use
it. Change implementation to instead make sure ${ACLOCAL_FLAGS}
gets passed to aclocal when called from the makefile.
* macros2/Makefile.am: alter installation so that it puts the
macros directly into $(datadir)/aclocal instead of
$(datadir)/aclocal/gnome2-macros
* autogen.sh (REQUIRED_AUTOMAKE_VERSION): use a modern version of
automake.
* macros2/gnome-compiler-flags.m4: move from compiler-flags.m4 to
reduce chance of collisions.
* macros2/gnome-autogen.sh: move from autogen.sh
* Makefile.am (SUBDIRS): don't build bin/ and macros/ directories.
* configure.in: don't create makefiles for bin/ and macros/
directories.
Since we don't actually build the support/ directory (since 2001),
remove the matching parts from the configure script.
2004-05-13 James Henstridge <james@daa.com.au>
* gnome-common.spec.in: simplify and update spec file.
2004-02-27 Sven Herzberg <herzi@abi02.de>
* macros2/autogen.sh: fix#135557
2004-02-17 Mark McLoughlin <mark@skynet.ie>
* doc-build/xmldocs.make: fix one last occurrence of
not using $(DESTDIR).
2003-10-02 Malcolm Tredinnick <malcolm@commsecure.com.au>
* doc-build/Makefile.am: Distribute README in place of the
non-existent ChangeLog. Doh!
* autogen.sh: Use the GNOME 2 autogen.sh script by default.
* configure.in: Version number bumped.
2003-08-23 Marco Pesenti Gritti <marco@gnome.org>
* macros2/compiler-flags.m4:
Define WARN_CXXFLAGS instead of overwriting
CXXFLAGS (like WARN_FLAGS).
2003-07-04 Frederic Crozat <fcrozat@mandrakesoft.com>
* macros2/compiler-flags.m4: don't use -Wsign-promo, it is
C++ only and causes warnings with gcc 3.3 when used on C.
2003-06-24 Marco Pesenti Gritti <marco@it.gnome.org>
* macros2/autogen.sh:
Remove --enable-compile-warnings from the default arguments
passed to configure because it break GNOME_COMPILE_WARNINGS
macro.
2003-05-24 Malcolm Tredinnick <malcolm@commsecure.com.au>
* MAINTAINERS: Put myself in as maintainer.
* configure.in: Bump the version number to 2.3.0
* configure.in, Makefile.am, macros2/autogen.sh, doc-build/*:
Add in the infrastructure to allow user documentatin to be built
from some common files. This will not affect existing packages.
The changes required to use this are given in doc-build/README.
2003-02-26 Frederic Crozat <fcrozat@mandrakesoft.com>
* macros2/autogen.sh: set WANT_AUTOCONF_2_5 variable to tell
Mandrake autoconf wrapper we want to check if autoconf 2.5x is here..
2003-02-18 Jody Goldberg <jody@gnome.org>
* configure.in : Don't depend on a file that James just deleted
2002-12-12 Jody Goldberg <jody@gnome.org>
* macros2/gnome-common.m4 (GNOME_DEBUG_CHECK) : now that autoconf-2.52
is a prereq for things the build broke on the use of
AC_DEFINE(GNOME_ENABLE_DEBUG)
without the additional arguments.
gnome-common contains a set of M4 macros useful to easily write configure
scripts for GNOME 1 and GNOME 2 programs. These macros provide a set of
checks used by many GNOME programs that need to do similar things.
