1 |
On Fri, 18 Sep 2015 13:33:08 +0200 |
2 |
hasufell <hasufell@g.o> wrote: |
3 |
|
4 |
> On 09/18/2015 01:32 PM, hasufell wrote: |
5 |
> > On 09/18/2015 01:14 PM, Alexis Ballier wrote: |
6 |
> >> On Fri, 18 Sep 2015 13:04:45 +0200 |
7 |
> >> hasufell <hasufell@g.o> wrote: |
8 |
> >> |
9 |
> >>> On 09/18/2015 12:56 PM, Alexis Ballier wrote: |
10 |
> >>>> On Fri, 18 Sep 2015 11:58:09 +0200 |
11 |
> >>>> hasufell <hasufell@g.o> wrote: |
12 |
> >>>> |
13 |
> >>>>> On 09/18/2015 11:55 AM, Duncan wrote: |
14 |
> >>>>>> Alexis Ballier posted on Fri, 18 Sep 2015 11:04:19 +0200 as |
15 |
> >>>>>> excerpted: |
16 |
> >>>>>> |
17 |
> >>>>>>>> Keep in mind what this implies when you change these |
18 |
> >>>>>>>> dependencies without bumping the ebuilds that use them. |
19 |
> >>>>>>> |
20 |
> >>>>>>> only way i see these changing is with a new ros_messages_*** |
21 |
> >>>>>>> useflag, which will cause a rebuild anyway |
22 |
> >>>>>> |
23 |
> >>>>>> ?? Only with --newuse or similar, tho? Otherwise USE (or |
24 |
> >>>>>> USE_EXPAND here) changes don't trigger rebuilds, do they? |
25 |
> >>>>>> |
26 |
> >>>>> |
27 |
> >>>>> Correct. It's not good to rely on this and expect users to have |
28 |
> >>>>> a certain update pattern or even use a particular PM. |
29 |
> >>>>> |
30 |
> >>>> |
31 |
> >>>> then they wont have the messages if they don't rebuild, and |
32 |
> >>>> cat/pkg[ros_messages_newthing] deps wont be satisfied and the pm |
33 |
> >>>> will do the right thing by rebuilding. |
34 |
> >>>> nothing to worry about, really. |
35 |
> >>>> |
36 |
> >>> |
37 |
> >>> cat/pkg[ros_messages_newthing] will not be in users VDB until you |
38 |
> >>> revbump cat/pkg, so I don't think it's that easy. |
39 |
> >>> |
40 |
> >> |
41 |
> >> and i think you're confused about what dynamic deps is and is not: |
42 |
> >> cat/pkg[ros_messages_newthing] is not in vdb, so is not satisfied, |
43 |
> >> so pm tries to find something that satisfies it from tree or dies. |
44 |
> >> |
45 |
> > |
46 |
> > I'm not confused about dynamic deps, but about your example, |
47 |
> > because you didn't say anything about revbumps. |
48 |
> > |
49 |
> > If cat/pkg is not (rev)bumped, then there will be no check about |
50 |
> > whether cat/pkg[ros_messages_newthing] is satisfied in the first |
51 |
> > place. |
52 |
> > |
53 |
> |
54 |
> correcting: if the package adding cat/pkg[ros_messages_newthing] is |
55 |
> not (rev)bumped |
56 |
|
57 |
yes, this one will be bumped, and this is not part of the eclass |