why the libraries are parted ?
Posted: 09 Dec 2011, 22:21
1st , ---> sorry for my bad , "very bad", english.
the question is that , why the libraries are dividev in 2 modules ??
i say ,the "usr/include" ,part of the libraries ...why put that on devel??
i know ..the usr/include part of the libraries are need only when try compile for update libraries...and think...put in devel module because that have the compilers """" no module devel , you no need usr/include parts""" OK,.
BUT ,when any one try update some librarie ...need remove the old 2 times ...one in the "active" , library are , and after in devel..for no "old" parts of the older librarie...or the old parts in devel..cause errors after other update..because overwirte the new library.
put example...
now ncurses are the last ..5.9 , this is now in core "active part" of the librarie..and usr/include part are on devel..
in the case of tomorrow exit ncurses 5.10 , and any one try update """""nice"""" , need remove 5.9 in core and in devel ...or when put 5.10 on core...the devel..overwrite newst part.
solution 1 .....same of now..all the people, part, and new usr/include parts inside devel. ( no, no no,,no like compress , uncompresss 2 big modules for 1 librarie update)
solution 2 (like more) , put the totally parts of the librarie in the module contains de log package , ..and when any one try update..only remove in the module of the log package are.
ROOT=uncompresed-module-directory removepkg var-log-packae-to-remove
the usr/include parts , only 5-10 megabits in xzm , i know the strategy are when peoplo no need module devel...minor size possible..no compilers , no "usr/include needs" , but i think..is a error.
today i updated , xorg-server , to 1.11.2 , mesalib to 7.11.2 , pixman to 0.24.0 , libdrm (all apis habilited) , xorg-drivers ...and some "protocol x headers" ...and now , have only 2 solutions ...put new modules on ""modules folder"" ..or work nice to remove originals...(xorg server module and DEVEL module usr/include parts) ...same work 2 times ...for 1 update....its no nice for developers.
think about.
thanks for your time ...sorry very large post.
the question is that , why the libraries are dividev in 2 modules ??
i say ,the "usr/include" ,part of the libraries ...why put that on devel??
i know ..the usr/include part of the libraries are need only when try compile for update libraries...and think...put in devel module because that have the compilers """" no module devel , you no need usr/include parts""" OK,.
BUT ,when any one try update some librarie ...need remove the old 2 times ...one in the "active" , library are , and after in devel..for no "old" parts of the older librarie...or the old parts in devel..cause errors after other update..because overwirte the new library.
put example...
now ncurses are the last ..5.9 , this is now in core "active part" of the librarie..and usr/include part are on devel..
in the case of tomorrow exit ncurses 5.10 , and any one try update """""nice"""" , need remove 5.9 in core and in devel ...or when put 5.10 on core...the devel..overwrite newst part.
solution 1 .....same of now..all the people, part, and new usr/include parts inside devel. ( no, no no,,no like compress , uncompresss 2 big modules for 1 librarie update)
solution 2 (like more) , put the totally parts of the librarie in the module contains de log package , ..and when any one try update..only remove in the module of the log package are.
ROOT=uncompresed-module-directory removepkg var-log-packae-to-remove
the usr/include parts , only 5-10 megabits in xzm , i know the strategy are when peoplo no need module devel...minor size possible..no compilers , no "usr/include needs" , but i think..is a error.
today i updated , xorg-server , to 1.11.2 , mesalib to 7.11.2 , pixman to 0.24.0 , libdrm (all apis habilited) , xorg-drivers ...and some "protocol x headers" ...and now , have only 2 solutions ...put new modules on ""modules folder"" ..or work nice to remove originals...(xorg server module and DEVEL module usr/include parts) ...same work 2 times ...for 1 update....its no nice for developers.
think about.
thanks for your time ...sorry very large post.