158267 – installsources should optionally create and install TAGS files

Bug 158267 - installsources should optionally create and install TAGS files

Summary: installsources should optionally create and install TAGS files

Status:	RESOLVED WONTFIX

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Enhancement/Feature Requests (show other bugs)
Hardware:	All Linux

Importance:	High enhancement
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2006-12-16 02:18 UTC by brad walker
Modified:	2007-01-10 01:17 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description brad walker 2006-12-16 02:18:08 UTC

i create TAGS files for sources installed under /usr/src/debug/<category>/<P> and include them in TAGS files for my projects. portage would be nicer if it could create TAGS on a per-package basis when using FEATURE installsources.

many projects define a make targets for tags. portage users should be able to specify a make.conf TAGS variable as ctags, etags, gtags, or other tagging systems. portage could have a fall-back mechanism for creating tags using any of the tagging systems.

Comment 1 Zac Medico gentoo-dev

2006-12-17 22:13:46 UTC

I think it would be best to make this some type of add-on rather than have portage be directly aware of it.  As it is, you can define a post_src_install function (user phase hook) in /etc/portage/bashrc and generate the tags there.

Comment 2 Marius Mauch (RETIRED) gentoo-dev

2007-01-10 01:17:48 UTC

Agreed, beyond portages scope.