4139 – Portage: add new config protection path

Bug 4139 - Portage: add new config protection path

Summary: Portage: add new config protection path

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	All Linux

Importance:	High enhancement (vote)
Assignee:	Daniel Robbins (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-06-25 09:25 UTC by Maik Schreiber
Modified:	2002-07-26 15:16 UTC (History)
CC List:	1 user (show)

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 Maik Schreiber 2002-06-25 09:25:50 UTC

Please add the path "/opt/jakarta/tomcat/conf" to CONFIG_PROTECT in
/etc/make.globals (this path is used by net-www/tomcat).

Comment 1 Daniel Robbins (RETIRED) gentoo-dev

2002-07-26 14:40:39 UTC

In Portage 2.0.18 and greater, you can use this modular approach to do it.  Add
an /etc/env.d/51tomcat file with this in it:

CONFIG_PROTECT="/opt/jakarta/tomcat/conf"

CONFIG_PROTECT is now incremental like USE, so old options won't get overwritten.
But the long-term solution is to get jakarta's config files in /etc/opt, which is
what the FHS tells us to do.  Maybe use a symlink and store jakarta config in
/etc/opt/tomcat/conf?  That's the best solution.

Comment 2 Maik Schreiber 2002-07-26 15:16:08 UTC

I think >=portage-2.0.18 should be added as a dependency then? That will have to
wait until an unmasked version of >=portage-2.0.18 is out then.