Bug 8510

Summary:	urpmi upgrade suggestions
Product:	Mageia	Reporter:	ra oeai <oeai>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	enhancement
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	urpmi	CVE:
Status comment:

Description ra oeai 2012-12-26 20:33:34 CET

Hi, well i'm usually open the software center and most of the time i'm waiting
- it is wrong
first of all searching installed packages should be worked in background service or in parallel thread, and it shouldnt be awaken each time you need just to save the snapshot of installed soft in different table maybe using the virtuoso database or just some xml like analog that will be spared for few tables, so the data can be accessed asap - first you need to load the basic tree - while doing this the background service can be started for checking persistence of modified folders and in parallel thread the tree will loading more deeply, and this can be used with getting data for packages, so the basic description can be set with updating all packages from rep and all i need is just to mark it for install, but when i marking it the downloading screen (that should be in background again) appears and i wait till it finishes and only then i can browse for other files and the package resolving dialog appears each time - and i wait again till it will resolve it, but this can be also be set in background, so i can see that i need to install some other files and i can just open the window after i will mark all needed packages and then it will resolve all packages together - and knowing my selection system can resolve some other dependencies so i don't need to choose alternatives since i have already choosed the package.
i just can't inspect the code, maybe will do it later - but you know... the code better than i do right now.

ra oeai 2013-01-04 03:22:34 CET

Summary: Software Center needs upgrade => urpmi upgrade suggestions

Comment 1 ra oeai 2013-01-04 03:24:32 CET

the other thing is to download and install packages in parallel thread without waiting till the end of installation process or finishing all downloads.
so when few independent packages are downloaded they can be started for installation while other process will continue to download other packages.

Comment 2 ra oeai 2013-01-04 17:15:45 CET

the one of the simplest mechanisms is to "touch" all libs and installed packages that are analyzed while "searching available packages" and then write the measured time into table of contents and list only new packages that were probably modified before or after and then touch folders, so next time just get the number of analyzed files before and get the number of files that exists on this moment and if it is different try to find out the situation by just taking "not in this date touched files" and then do other things, actually the "locate -c" can do some part of the trick.

Manuel Hiebel 2013-01-04 17:53:13 CET

Source RPM: rpmdrake? => urpm

Manuel Hiebel 2013-01-04 17:53:21 CET

Source RPM: urpm => urpmi

Comment 3 ra oeai 2013-01-06 00:15:12 CET

and also let's assume that people actually will not use self-compiled packages in more than 80% of cases, so there's no need of scanning each time packages - but just put one more bool field in the packages table.
and for advanced users - this should be just a simple button @rescan_packages and actually there could be a kind of dialog so they can choose a directory to scan or simply write the path into string and it will be parsed.
because many advanced users that knows baout how to compile it will actually like that function and by doing that it would be nice to parse source and makefiles to resolve dependencies and create a package automatically if it is newer (but this maybe faulty because of manual patching it it's better to do that in package creating program)

Manuel Hiebel 2013-01-27 00:57:15 CET

Severity: normal => enhancement

Comment 4 Marja Van Waes 2015-04-16 22:31:25 CEST

Sorry, but this bug saw no action since over 2 yrs ago - no cauldron package has stayed the same - and is still assigned to Bug Squad.

Closing as OLD

Please reopen if this report is still valid for _current_ cauldron and/or fully
updated Mageia 4

Status: NEW => RESOLVED
Resolution: (none) => OLD