| 1 |
-- Riyad Kalla <rsk@×××××××××.edu> spake thusly: |
| 2 |
|
| 3 |
>> -----Original Message----- |
| 4 |
>> From: Brian Friday [mailto:bfriday@××××××××.edu] |
| 5 |
>> |
| 6 |
>> I agree as well, the example I gave earlier of a possible XML |
| 7 |
>> package file was based on my incorrect assumption portage |
| 8 |
>> was python and not bash based. Not sure why I got that |
| 9 |
>> impression, especially as I realize all the conf files have |
| 10 |
>> bash syntax... |
| 11 |
|
| 12 |
> come to think of it, I thought it was all python as well.... |
| 13 |
> |
| 14 |
> anybody know why we thought this? |
| 15 |
|
| 16 |
Portage itself is implemented in Python, but the ebuild mechanism is |
| 17 |
all done with shell scripts. It goes something like: |
| 18 |
|
| 19 |
emerge [python] loads: |
| 20 |
portage.py [python] and calls |
| 21 |
portage.doebuild() [python] which executes |
| 22 |
ebuild.sh [shell] which sources |
| 23 |
category/pkg/pkg-version.ebuild [shell] |
| 24 |
|
| 25 |
The line is pretty blurred between the two though, so I could certainly |
| 26 |
understand the confusion. |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-dev@g.o mailing list |
Archives