| 1 |
On Thu, Oct 26, 2006 at 02:24:45PM -0400, Daniel Barkalow wrote: |
| 2 |
> It would be useful if ebuilds listed any USE flags that don't affect the |
| 3 |
> package the ebuild is for, so that emerge knows it doesn't need to rebuild |
| 4 |
> the package if these change (or are newly added to the ebuild). These |
| 5 |
> include flags like "glibc-compat20" and "nptl" on glibc-2.4-r3 (if they |
| 6 |
> aren't set correctly, it just doesn't build, because this version doesn't |
| 7 |
> support other configurations, but the USE flag is there so you don't |
| 8 |
> blindly lose some obsolete feature you needed), or "minimal" on (e.g.) |
| 9 |
> xinit (which affects RDEPEND, but not anything else). |
| 10 |
|
| 11 |
Portage would have to preparse the ebuild and get all contexts where a |
| 12 |
condition based on a `use'-result occurs. |
| 13 |
|
| 14 |
> It's obviously not important for correctness, but it would save a whole |
| 15 |
> lot of time, because it seems to be mostly big packages that end up with |
| 16 |
> these, and ignoring them is a pain when you actually change a meaningful |
| 17 |
> global USE flag and want to rebuild everything that's actually |
| 18 |
> different. |
| 19 |
|
| 20 |
I think it's not correct to rebuild a package without need. |
| 21 |
|
| 22 |
Hannes |
Archives