| 1 |
On 1/25/12 10:23 AM, Thomas Kahle wrote: |
| 2 |
> I suggest that emerge could signal its various failures via return |
| 3 |
> codes. That would be useful in automated archtesting: |
| 4 |
> |
| 5 |
> https://bugs.gentoo.org/show_bug.cgi?id=400705 |
| 6 |
|
| 7 |
My opinion is very similar to what Brian Harring said on that bug: some |
| 8 |
Python API would be much better than still pretty vague return code |
| 9 |
(what would you do with it?). |
| 10 |
|
| 11 |
Some ideas: |
| 12 |
|
| 13 |
- I emerge a list of packages, some unstable dependencies are required; |
| 14 |
allow me to get a list of those package atoms |
| 15 |
|
| 16 |
- same as above, but return list of USE flags adjustments required |
| 17 |
|
| 18 |
- package blocks |
| 19 |
|
| 20 |
- unsatisfied USE flag constraints |
| 21 |
|
| 22 |
... and so on. I think it can start very simple and small, and be |
| 23 |
extended as needed. |
Archives