| 1 |
On 5/16/21 12:53 PM, Andreas Fink wrote: |
| 2 |
> On Sun, 16 May 2021 12:49:26 +0200 |
| 3 |
> n952162 <n952162@×××.de> wrote: |
| 4 |
> |
| 5 |
>> On 5/16/21 11:28 AM, Neil Bothwick wrote: |
| 6 |
>>> On Sun, 16 May 2021 11:26:37 +0200, n952162 wrote: |
| 7 |
>>> |
| 8 |
>>>>>> There are no use flags defined for any of the packages I did a random |
| 9 |
>>>>>> check for, either on the server or the client. I am worried that it |
| 10 |
>>>>>> is as you say: that the ebuild has a change of USE flags, which, of |
| 11 |
>>>>>> course, has nothing to do with me, the user. |
| 12 |
>>>>> As already stated, any USE flag changes would appear in the emerge |
| 13 |
>>>>> output, this is most likely caused by --changed-deps. Try with |
| 14 |
>>>>> --changed-use but without --changed-deps to see. |
| 15 |
>>>>> |
| 16 |
>>>>> |
| 17 |
>>>> I have introduced that into my build script. But, if it's as you say, |
| 18 |
>>>> the one is a subset of the other, it should have no effect on the |
| 19 |
>>>> output, right? |
| 20 |
>>>> |
| 21 |
>>> --changed-use is a subset of --newuse. --changed-deps is separate. |
| 22 |
>>> |
| 23 |
>>> |
| 24 |
>> Ah, I oversaw that. |
| 25 |
>> |
| 26 |
>> Ah. why would I want to have --changed-deps anyway? That suddenly seems |
| 27 |
>> silly. |
| 28 |
>> |
| 29 |
>> It's unfortunate, if there's no explanatory display if a package got |
| 30 |
>> disqualified for that reason. |
| 31 |
>> |
| 32 |
>> |
| 33 |
|
| 34 |
Trying to comprehend here... |
| 35 |
|
| 36 |
> If you want to have a binhost, then --changed-deps will become |
| 37 |
> "necessary" at some point. Let me draw you a picture, where a binhost |
| 38 |
> would fail to provide the correct package: |
| 39 |
> - Binhost builds on day 1 package XYZ(i.e. server updates from internet) |
| 40 |
> - computer that would merge with packages from binhost is NOT updated(client does NO emerge on that day) |
| 41 |
> - the dependencies are changed on day 2(i.e. XYZ is emerged onto server, with changed dependencies in the ebuild) |
| 42 |
> - Binhost does NOT rebuild, because you do not have --changed-deps |
| 43 |
> enabled on day 2*(what is "Binhost" here? The --changed-deps is specified on the client)* |
| 44 |
> - Computer that merges from the binhost is updated on day 2 but will |
| 45 |
> NOT use the binary package from binhost, because the dependencies do |
| 46 |
> not match |
| 47 |
> There are flags to ignore dependency mismatches, but the default would |
| 48 |
> just not use the binary package. |
| 49 |
> |
| 50 |
> Cheers |
| 51 |
> Andreas |
| 52 |
> |
| 53 |
What does changed-deps mean, actually? |
| 54 |
|
| 55 |
--changed-deps [ y | n ] |
| 56 |
Tells emerge to replace installed packages for which |
| 57 |
the corresponding |
| 58 |
ebuild dependencies have changed since the packages were |
| 59 |
built. ... |
| 60 |
|
| 61 |
I presume it means that a package needed XYZ before, but now needs |
| 62 |
XYZZ. If I don't specify --changed-deps, that I might get a run-time |
| 63 |
resolution problem. |
| 64 |
|
| 65 |
Or, does it mean that the package specified XYZ.1 in an excess of |
| 66 |
precision and the new version specifies XYZ.3? |
| 67 |
|
| 68 |
I just ran into this: |
| 69 |
|
| 70 |
--binpkg-changed-deps [ y | n ] |
| 71 |
Tells emerge to ignore binary packages for which the |
| 72 |
corresponding ebuild |
| 73 |
dependencies have changed since the packages were built. |
| 74 |
In order to help |
| 75 |
avoid issues with resolving inconsistent dependencies, |
| 76 |
this option is auto- |
| 77 |
matically enabled unless the --usepkgonly option is |
| 78 |
enabled. Behavior with |
| 79 |
respect to changed build-time dependencies is controlled |
| 80 |
by the --with-bdeps |
| 81 |
option. |
| 82 |
|
| 83 |
But I haven't figured out what it means yet. In particular, what all |
| 84 |
the stated implications mean. |
Archives