[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gen-tagging-method [Was: [Gnu-arch-users] unmatched files]

From: Andrew Suffield
Subject: gen-tagging-method [Was: [Gnu-arch-users] unmatched files]
Date: Mon, 17 Nov 2003 00:51:27 +0000
User-agent: Mutt/1.5.4i

On Sun, Nov 16, 2003 at 11:27:22PM +0000, Andrew Suffield wrote:
> On Sun, Nov 16, 2003 at 05:38:44PM -0500, Colin Walters wrote:
> > "untagged-source" was a nice step forward.  However, it still isn't
> > enough to just use "untagged-source precious" with say an
> > autotools-using project.  That's because .deps and .libs don't match any
> > regexp, and are thus categorized as unrecognized, which is an error. 
> > The user won't be able to commit until they do something about this.
> What you want is a =tagging-method file that comes arranged for
> auto{conf,make} in advance. I have one of those in my ~ someplace. I
> thought about distributing it, but rapidly realised that you want
> different files depending which tools you use - autoconf is pretty
> common, but any of the following can also be used and introduce new
> things that you want in the regexps: automake, gettext, libtool,
> dejagnu, etc...
> What I've been meaning to do is write a little perl script that
> generates =tagging-method files based on a set of options. I think
> I'll go and do that now, actually.

And done. address@hidden/gtm--main--0

address@hidden:~/arch/gtm$ ./gen-tagging-method autoconf automake libtool gcc
untagged-source precious
source (^[_=a-zA-Z0-9].*$)
unrecognized ()
junk (,.*)
backup (~$|\.~[0-9]+~$|\.(bak|orig|rej|original|modified|reject)$)

  .''`.  ** Debian GNU/Linux ** | Andrew Suffield
 : :' : |
 `. `'                          |
   `-             -><-          |

Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]