Ebuilds and Handling /etc/profile

[Demosthenex]

What is the best way to handle modifications to /etc/profile from an ebuild?

I'm creating an ebuild that absolutely must add a few lines to /etc/profile, but not just environment variables. That rules out /etc/env.d/.

Just tacking on lines at the end is, well, tacky! Not to mention hard to remove at a later date (ie. unmerge or upgrade).

Shouldn't there be something like env.d for profile, or better yet, let env.d be standard shell scripts instead of lists of environment variables?

Comments/suggestions/ideas?

Demo

[pjp]

What is it you are trying to do? That might help for possible solutions.

What is relying on something that needs to change it? Seems odd.
_________________
Quis separabit? Quo animo?

[Naan Yaar]

bash-completion does this instead:

[Demosthenex]

I'm propogating some of my shell aliases and some environment variables that should be for root only across multiple Gentoo boxes.

ie: if [ ${UID} = 0 ] then export ...

I want to use portage for change management and syncronization.

I like the idea of /etc/profile.d, but if nothing else calls it then I'm just polluting /etc... Plus the point of altering the system profile is to prevent having to fuss with individual user profiles.

Obviously I don't like the idea of directly editing the files for change management reasons.

Further suggestions?

Demo

[Naan Yaar]

profile.d is already used by bash-completions and medusa; so there is some precedence for putting it in there. Unfortunately, there is no mechanism in /etc/profile in gentoo to source things in profile.d (RedHat has this); this bug tracks the issue.