1 |
El jue, 20-09-2012 a las 18:55 +0100, Ciaran McCreesh escribió: |
2 |
> On Thu, 20 Sep 2012 19:54:43 +0200 |
3 |
> Pacho Ramos <pacho@g.o> wrote: |
4 |
> > That isn't necessary what could occur if the behavior changes |
5 |
> > unexpectedly: as current behavior is already being assumed in |
6 |
> > eclasses/ebuilds, portage couldn't change it without, before, porting |
7 |
> > ebuilds/eclasses to use that new hypothetical behavior. |
8 |
> |
9 |
> Sure it can. Portage supports what's in the spec. If you're relying |
10 |
> upon undefined behaviour, it's your problem when it stops working. |
11 |
> |
12 |
|
13 |
It cannot break the tree, only square-headed people can think somebody |
14 |
would force a breakage and don't try to fix it before. |