Hi,
Having just completed the migration on two systems I found some things
which concerns me:
1. A default/linux/amd64/17.0/desktop to
default/linux/amd64/17.1/desktop. This differs from the no-multilib in
that there are symlinks now for the various lib32 to lib. No such
symlinks on the no-mulilib systems (this makes sense, but why is lib32 a
symlink back to lib/)
2. If /usr/local/lib* doesn't exist the script bails out. This only
happened on one of the two systems I did now, specifically the
default/linux/amd64/17.0/no-multilib =>
default/linux/amd64/17.1/no-multilib one. Other systems I've just
checked seems to already have this by virtue of
/usr/local/lib{64,32}/.keep existing, but no owners of the files, so
this could be sheer dump luck. Which is never good. Sorted by manually
creating lib32 and creating the symlink as instructed. Post migrate
there is a lib/ and lib64/ folder. The complaint on this was about
/usr/local/lib32 if I recall correctly
What is the actual "target" objective with the change? I would have
expected (not being one to follow this too closely):
lib/ - arch independent stuff (eg, netifrc / dhclient etc scripts).
lib32/ - 32-bit specific stuff (libs for 32-bit).
lib64/ - 64-bit specific stuff (libs for 64-bit).
What am I missing?
Kind Regards,
Jaco
On 2020/10/22 21:16, Andreas K. Hüttel wrote:
> Am Donnerstag, 22. Oktober 2020, 18:44:48 EEST schrieb Michał Górny:
>> On Thu, 2020-10-22 at 11:17 -0400, Brian Evans wrote:
>>> Users frequently are choosing the wrong profile versions in new installs
>>> and accidentally downgrading to 17.0 with some saying they see it first.
>>>
>>> A simple reordering could help new installs.
> Independent of this useful change, it's probably time to deprecate the amd64
> 17.0 profiles!
>
