| 1 |
El mié, 06-06-2012 a las 18:19 +0100, Ciaran McCreesh escribió: |
| 2 |
> On Wed, 06 Jun 2012 10:32:08 +0200 |
| 3 |
> Pacho Ramos <pacho@g.o> wrote: |
| 4 |
> > > We do? Please tell us. I was under the impression that we still |
| 5 |
> > > didn't fully know what the problem was. |
| 6 |
> > |
| 7 |
> > Well, could you please let me know how to handle some issues already |
| 8 |
> > mentioned? For example: |
| 9 |
> > - Rebuild dbus-glib and gobject-introspection after major glib update. |
| 10 |
> > - Rebuild x11 drivers after xorg-update |
| 11 |
> |
| 12 |
> Those are the ones we probably do understand. You just up the SLOT (and |
| 13 |
> if you really need to, use blockers between slots, although this is |
| 14 |
> discouraged in favour of writing better ebuilds), and everything that |
| 15 |
> build+run-deps upon these things uses := dependencies. |
| 16 |
> |
| 17 |
> > - Rebuild python/perl/ocaml stuff after python/perl/ocaml update |
| 18 |
> |
| 19 |
> That depends. If you only have to do it after an upgrade, same |
| 20 |
> solution. If you have to do it with a rebuild too, then that's one of |
| 21 |
> the situations I claim we don't fully understand because no-one has |
| 22 |
> specified what the exact general problem is (although lots of people |
| 23 |
> have looked at one particular case and assumed that their case holds |
| 24 |
> for everything, which isn't true). |
| 25 |
> |
| 26 |
|
| 27 |
I think they are only needed on upgrades, not rebuilds, but I cannot |
| 28 |
assure that, probably their maintainers will know better :) |
Archives