After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 311951 - gnome-autogen makes a mess of my backups
gnome-autogen makes a mess of my backups
Status: RESOLVED FIXED
Product: gnome-common
Classification: Core
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: Gnome Common Maintainer(s)
Gnome Common Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2005-07-29 11:29 UTC by Tommi Vainikainen
Modified: 2005-09-20 06:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tommi Vainikainen 2005-07-29 11:29:57 UTC
Current gnome-autogen contains line
  configure_files="`find $srcdir -name '{arch}' -prune -o -name configure.ac
-print -o -name configure.in -print`"
(Notice the kludge for Arch.)

I'm using quilt (http://savannah.nongnu.org/projects/quilt/) to make clean
patches I can send to Bugzilla. To manage patches quilt makes backup copies
under .pc directory. Now the find command in gnome-autogen uses
configure.(in|ac) from the backup which is not very nice.

If there is not many projects which use multiple configure.(in|ac), I'd like to
suggest to test only topdir for configure.(in|ac), and use some env variable to
specify multiple configures. If you think this is not acceptable, at least the
find command should skip every directory name beginning with dot ('.'), so that
backups et cetera are skipped.

Here is a find command that should skip enough
configure_files="`find $srcdir -name '{arch}' -prune -o -path '*/.*' -prune -o
-name configure.ac -print -o -name configure.in -print`"
Comment 1 James Henstridge 2005-08-16 11:09:08 UTC
I suppose the best fix for this would be to look in the configure files to
detect nested projects like this.

This would involve looking for AC_CONFIG_SUBDIRS() calls, and only checking
those directories.
Comment 2 James Henstridge 2005-09-20 06:05:58 UTC
I've committed a fix for this, pruning directories with names matching ".?*"
(which won't match ".").  This seems like a good safety measure, since it will
also avoid the bookkeeping directories for Bazaar-ng (.bzr) and Subversion (.svn).