gnu-arch-users
[Top][All Lists]
Advanced

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

[Gnu-arch-users] Some questions regarding tagging :)


From: Magnus Therning
Subject: [Gnu-arch-users] Some questions regarding tagging :)
Date: Thu, 4 Sep 2003 17:30:22 +0200
User-agent: Mutt/1.5.4i

I am rather new on the list, so I might have missed some old postings
that covered these questions.

I am trying to take a SW package managed with CVS upstream and make
local changes using tla for my own work. The package is configured and
built using automake.

I would like to use tagline as the tagging-method, ala miles-emacs.
Ideally I would be able to convince upstream to include them so I can
track them easier.

Regarding tagging and taglines:

- It seems rather silly that m4 comments don't work for tag-lines:
  'dnl arch-tag: my tag' does nothing for 'tla inventory --tags'.
  Is this (being) fixed?

- I am somewhat struggling with what files to put a tag line in. Does
  anyone have any insights on this? Automake forces quite some extra
  files to exist (AUTHORS, NEWS, ChangeLog, etc). Putting tag-lines in
  them isn't really a problem, but it will make them look different from
  the corresponding files of other packages. There are also some files
  that have a prescribed format (e.g. Debian changelog files) where a
  tag-line wouldn't be acceptable, should such files be added manually
  instead?

- Should directories be added explicitly when using tag-lines?

- When using Automake during development quite a few files are generated
  among the sourcefiles from running auto{header,make,conf} and
  libtoolize. Has anyone written some nice regexps to handle this,
  rather irritating behaviour?

/M

BTW I am using tla 1.0.6 from Debian unstable.

-- 
Magnus Therning  mailto:address@hidden
+31-40-2745179  http://pww.innersource.philips.com/magnus/
OpenPGP:0x4FBB2C40

It is not the strongest of the species that survive, nor the most
intelligent, but the one most responsive to change.
     -- John McFee

Attachment: pgplip228CyQq.pgp
Description: PGP signature


reply via email to

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