| 1 |
Hi, |
| 2 |
|
| 3 |
How about using the existing portage/ebuild.sh functionality to interface |
| 4 |
python to bash and source the ebuilds? It would make the checks more |
| 5 |
powerful, incl. things like undefined strings and functions and eclass |
| 6 |
support. |
| 7 |
|
| 8 |
It would also make it easy to make sure the file is an ebuild. Right now you |
| 9 |
can get results like: |
| 10 |
--- |
| 11 |
bash-2.04# ./ebuildchecker.py --no-total /usr/bin/mkdir |
| 12 |
/usr/bin/mkdir : OK |
| 13 |
--- |
| 14 |
This may not be important, but if you accidentally pass a non-ebuild as a |
| 15 |
parameter, you won't get an error. |
| 16 |
|
| 17 |
This is off the top of my head, but it may be reasonable. What do you think? |
| 18 |
|
| 19 |
Oh, and another thing: options are only recognized before the ebuild list, |
| 20 |
they have no effect when put between or after the ebuilds listed. This can be |
| 21 |
somewhat confusing at first. |
| 22 |
|
| 23 |
-- |
| 24 |
|
| 25 |
Dan Armak |
| 26 |
Gentoo Linux Developer, Desktop Team |
| 27 |
Matan, Israel |
Archives