Bug 9419 - libX structure
Summary: libX structure
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-16 05:26 CET by ra oeai
Modified: 2015-04-30 22:38 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description ra oeai 2013-03-16 05:26:09 CET
i'm still thinking of changes of lib-root
 should i write about it in dev list?
 the thing is pretty much easy though it's about moving all native kernel libs in /usr/lib directory and all compatible into /usr/lib/x and for different kernels this could be /usr/lib/x/i586 ~x/i686 ~x/i786 where i586 are kernels for old school machines with only 1core and i686 for >=2core but x32, and i786 are for x64 and one more is ~x/a7 + ~x/i7 meaning intel + amd using i786=x64 multicore but specialised for those sort of vendors
 so if crosskernelLib will be able to work with kernel it will not go into all/lib but will be placed into special folder
 but all real Libs for this kernel will be in /usr/lib and lib sorting will be done actually by urpmi settings so x64Libs will have a usual libSomeLib name without x64 because program knows exactly arch of lib
 and all programs that can be just compiled they will have a usual placement in /usr/lib and lib parsing can be done while actually negotiation with repo server is happenning
 so users mostly don't need to choose 32 or 64 repo this will be the analysis thing
 they will need only to take stable testing backport and tainted
 repos and choose maybe few mirrors to search for
 so for developers only architecture and repo load can be revealed with some easy checkbox
 and this can be done also if user is taking devel packages
 for developers i mean
 package compatibility tool i think can be written
 and maybe this is already in solving state
 or maybe is already somewhere built
 i mean lib Xcompatible
 well of course this is not for this release i think
 will need to recompile almost everything i guess but actually this can be solved with just a few hardlinks
 that after upgrade of all packages can just disappear
 magically
 i can tell you more actually we already have a8 architecture with more than 8 cores so parallel threads and many more can be used absolutely new way there
 and this means that kernels can be resharped very much and for many thread Libs will be needed really new compiler maybe
 so separating libs can be useful, but right now it's done not like it should be, because kernel and compilers acts with lib64 while their native lang is x64 also, they should work with just /lib and all others need to be separated 
,~, \|/

Reproducible: 

Steps to Reproduce:
Comment 1 Thierry Vignaud 2015-04-30 22:38:19 CEST
Not a bug...

Status: NEW => RESOLVED
CC: (none) => thierry.vignaud
Resolution: (none) => WONTFIX


Note You need to log in before you can comment on or make changes to this bug.