| 1 |
On Tue, 2020-11-10 at 09:53 +0100, Fabian Groffen wrote: |
| 2 |
> On 10-11-2020 09:49:27 +0100, Michał Górny wrote: |
| 3 |
> > > > So what you're saying is that you've had the wrong value of SYMLINK_LIB |
| 4 |
> > > > for ages, and now you've created a meaningless 17.1 profile that chnages |
| 5 |
> > > > it but isn't actually supposed to change anything, correct? |
| 6 |
> > > |
| 7 |
> > > I guess, because the amd64 17.0 profile is deprecated with force, and I |
| 8 |
> > > had to do something ... |
| 9 |
> > |
| 10 |
> > Now that's a lie. Only the regular amd64 profiles are deprecated. |
| 11 |
> > There are no deprecation notices e.g. in the x32 profile or prefix |
| 12 |
> > profiles. |
| 13 |
> |
| 14 |
> Our profiles either directly depend on the amd64/17.0 profile, or we use |
| 15 |
> a sub-profile from amd64/17.0 profile, so if it's going to get removed, |
| 16 |
> we are having a problem, don't we? |
| 17 |
|
| 18 |
It isn't going to be removed as long as other profiles depend on it. |
| 19 |
It'll probably be re-parented. |
| 20 |
|
| 21 |
-- |
| 22 |
Best regards, |
| 23 |
Michał Górny |
Archives