1 |
On Fri, 24 Oct 2014 16:22:15 -0700 |
2 |
Zac Medico <zmedico@g.o> wrote: |
3 |
|
4 |
> In /etc/portage/profile, we already have support for using directories |
5 |
> in the place of regular config files (portage1_directories = True). |
6 |
> So, go ahead and enable package.bashrc there too. |
7 |
> |
8 |
> We could also support /etc/portage/package.bashrc, but that would be |
9 |
> more complicated since /etc/portage/bashrc is the long-standing |
10 |
> location of the user's bashrc which applies to all packages, and |
11 |
> package.bashrc would instead expect /etc/portage/bashrc to be a |
12 |
> directory containing per-package bashrc files. So for now, we only |
13 |
> support package.bashrc inside /etc/portage/profile. |
14 |
> --- |
15 |
> pym/portage/package/ebuild/_config/LocationsManager.py | 3 ++- |
16 |
> 1 file changed, 2 insertions(+), 1 deletion(-) |
17 |
> |
18 |
> diff --git a/pym/portage/package/ebuild/_config/LocationsManager.py |
19 |
> b/pym/portage/package/ebuild/_config/LocationsManager.py index |
20 |
> 8bf321c..6280a42 100644 --- |
21 |
> a/pym/portage/package/ebuild/_config/LocationsManager.py +++ |
22 |
> b/pym/portage/package/ebuild/_config/LocationsManager.py @@ -132,7 |
23 |
> +132,8 @@ class LocationsManager(object): self.user_profile_dir = |
24 |
> custom_prof self.profiles.append(custom_prof) |
25 |
> self.profiles_complex.append( |
26 |
> - _profile_node(custom_prof, |
27 |
> True, True, ())) |
28 |
> + _profile_node(custom_prof, |
29 |
> True, True, |
30 |
> + ('profile-bashrcs',))) |
31 |
> del custom_prof |
32 |
> |
33 |
> self.profiles = tuple(self.profiles) |
34 |
|
35 |
|
36 |
I'm a little confused. Is this a fix for Bertrands bashrc patches |
37 |
already applied? Or is it unrelated? |
38 |
-- |
39 |
Brian Dolbec <dolsen> |