1 |
On Wed, Sep 14, 2005 at 11:06:03AM -0500, Kito wrote: |
2 |
> |
3 |
> On Sep 13, 2005, at 3:58 PM, Grobian wrote: |
4 |
> [...] |
5 |
> |
6 |
> ># This script searches for executable script files in the given |
7 |
> ># directory and all its sub-directories and tries to process them in |
8 |
> ># such a way, that the actual PATH environment controls how they are |
9 |
> ># executed. An example would be a script file having at the first |
10 |
> >line: |
11 |
> |
12 |
> Ok, I was thinking something along these lines to handle |
13 |
> install_names for executables and dylibs as well, basically just loop |
14 |
> over the ${D} and either warn or fix if install_names contain paths |
15 |
> outside the global prefix. |
16 |
> |
17 |
> Brian: Is this sort of thing best handled in bash ala bashrc, or is |
18 |
> there a good entry point in the portage code to plug this stuff in |
19 |
> pythonically? |
20 |
|
21 |
Kicking around something that would allow setups the ability to plug in |
22 |
chunks of code for doing things prior/post merge... |
23 |
|
24 |
So, hooking within the python side would be possible, and prefered. |
25 |
Basically is how collision-protect/setuid scans will be implemented, |
26 |
and probably triggering ldconfig runs even (assuming it works sanely). |
27 |
|
28 |
Less cruft jammed into bash, the better. :) |
29 |
~harring |