![](https://seccdn.libravatar.org/avatar/f56c176084ab8879a9b598c3046527c2.jpg?s=120&d=mm&r=g)
as currently using a twin cpu e52680 0 (v0) 64bit as my main workstation i know im going to be affected by this , its also got a rtx3080 gpu in there , using it for game design with unreal 5 engine and suse tumbleweed , as specs for machines go it still beats current cheap shop bought pcs spec and speed wise in most cases but like many users doing such , or blender type apps the use of old ex lease workstations is the only choice they have its not like there 20 + year old x586s or 32bit only , support for them is still needed so i dont advocate the dropping of v0 and v1 64bit cpus maybe a solution would be adding sufixes to the package managment of the rpms , I.E. _xvx as follows libthis-x64-1-2-93_xvx.rpm (in the main package list) but the the server holds .. libthis-x86-1-2-93_x0x.rpm (v0) libthis-x86-1-2-93_x2x.rpm (v2 or above) where _xvx is the suffix the cpu version is checked and the highest value avalable not greater than the tested version is installed so later when you want to add v3 or v4 or greater optimisations then add libthis-x86-1-2-93_x3x.rpm (v3) libthis-x86-1-2-93_x4x.rpm (v4 or above) although it may increase the server storage needed to hold the libs , and the load in compiling them it should offset the download bandwith on updates as only one is needed per system and provide the needed performance increase for those using grater than the v0 versions , it could be expanded on in future if other issues arrise say amd v5 ver intel v5 to say _xa5x and _xi5x if they do part ways on best optimisation methods adding a cpu test version option to yast (do once and set installed to that ) means unless you upgrade the cpu then its set (maybe a force version option to allow forced system wide installation to a lower version where v3 may have got installed by error on a v2 ) im shure that it should not be too hard to impliment that way , but i do understand the server storage increase may be an issue at the same if done this way it would be posible to guage the number of users on a spesific cpu version by the number of version spesific downloads , so in future you would know the percentage user base of a spesific version so it should not be two hard to find a way