| 1 |
On Mon, 18 May 2009 17:47:52 +0300 |
| 2 |
Petteri Räty <betelgeuse@g.o> wrote: |
| 3 |
> Ciaran McCreesh wrote: |
| 4 |
> > On Mon, 18 May 2009 13:04:27 +0300 |
| 5 |
> > Alex Alexander <alex.alexander@×××××.com> wrote: |
| 6 |
> >> Unfortunately we've got reports from paludis users stating that |
| 7 |
> >> they can't update QT from qting-edge anymore. |
| 8 |
> > |
| 9 |
> > Paludis treats blocks as strong, the way Portage used to and the way |
| 10 |
> > PMS defined them until we had to retroactively change it to allow |
| 11 |
> > Portage's newer behaviour... |
| 12 |
> |
| 13 |
> Unfortunate but what does this have to do with the original question? |
| 14 |
> EAPI 2 moved to the new soft behavior and as far as I know all qt |
| 15 |
> ebuilds are EAPI 2. |
| 16 |
|
| 17 |
The definition of soft behaviour allows soft blockers to be treated |
| 18 |
identically to hard blockers. We had to do it this way because |
| 19 |
Portage's rules for soft blockers are too fuzzy and arbitrary to turn |
| 20 |
into a formal specification -- they were a "code first, think later" |
| 21 |
solution with which we can't do anything useful. |
| 22 |
|
| 23 |
-- |
| 24 |
Ciaran McCreesh |
Archives