| Server IP : 101.53.144.229 / Your IP : 216.73.216.181 Web Server : Apache System : Linux host.gdigitalindia.in 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 User : digitalshiksha ( 1179) PHP Version : 5.6.40 Disable Function : eval,show_source,system,shell_exec,escapeshellarg,escapeshellcmd,proc_close,proc_open,ini_alter,dl,show_source,curl_multi_exechellcmd, ini_restore,apache_get_modules,get_cfg_var,passthru, exec ,proc_get_status,fpassthru,c999_buff_prepare,c999_sess_put,c99_buff_prepare,c99_sess_put,proc_close,ini_alter,dl,symlink,link,proc_close,ini_alter,dl,symlink,link,mail MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/doc/yum-metadata-parser-1.1.4/ |
Upload File : |
YUM metadata parser written in C. * Why? The biggest complaint people have with YUM is often the performance of parsing the metadata. This implementation should be ~10 times faster, parsing the primary.xml file under 1 second usually, filelists.xml under 3 seconds and other.xml under 4 seconds. It uses a lot less memory as well, some testings I have done show it uses ~4mb instead of 40mb standard YUM uses. * How? Should be really easy: python setup.py build sudo python setup.py install --prefix=/usr (Assuming you python prefix is /usr). The next time you use yum, it regenerates the sqlitecache because the database schema is slightly different.