1 |
Brian Harring wrote: |
2 |
>> Brian: Is this sort of thing best handled in bash ala bashrc, or is |
3 |
>> there a good entry point in the portage code to plug this stuff in |
4 |
>> pythonically? |
5 |
> |
6 |
> Kicking around something that would allow setups the ability to plug in |
7 |
> chunks of code for doing things prior/post merge... |
8 |
> |
9 |
> So, hooking within the python side would be possible, and prefered. |
10 |
> Basically is how collision-protect/setuid scans will be implemented, |
11 |
> and probably triggering ldconfig runs even (assuming it works sanely). |
12 |
> |
13 |
> Less cruft jammed into bash, the better. :) |
14 |
> ~harring |
15 |
|
16 |
I personally think this script should be seen as 'proof-of-concept'. |
17 |
It's not too fast, and it involves a lot of inefficient work. I'm no |
18 |
python coder, but I think, given this 'proof-of-concept' it may be |
19 |
fairly simple to write a function (?) or two in python that performs |
20 |
this job a few orders of a magnitude faster and more controllable. |
21 |
|
22 |
The problem with these kinds of scripts is that their portability is not |
23 |
really assured. I dubbed whether I would write a quick C version, but |
24 |
again I stumbled upon the portability question and decided not to do so, |
25 |
because portage, as inner core of Gentoo, should be as much as possible |
26 |
unaffected by environmental differences. Python is (like Java) a |
27 |
solution to that. So, ultimately, this script should be rewritten in |
28 |
Python. |
29 |
|
30 |
|
31 |
-- |
32 |
Fabian Groffen |
33 |
Gentoo for Mac OS X |
34 |
-- |
35 |
gentoo-osx@g.o mailing list |