-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ok seeing Its now feature request/suggestion time (by which I mean the sudden surge in threads about features rather than bugs) I'll join in with a few Ideas that might improve things.
1)I'd like to see some new features to urpmi most of which others have already mentioned: - - resume on partial downloads as the default behavior - - rsync support (if it isn't already present) - - support for multiply mirror choosing the fastest/local ones first - - src.rpm compilation and installation. I'd like to be able to set up urpmi to use a source RPM they way it currently uses mandrake rpm repositories. I'd like to be able to install a simply BASE system a kernel, the basic libraries, gcc and other needed tools, Mandrake tools and urpmi. Then simply type some thing along the lines of urpms (urpmi for SRPMS) urpms –flags=”--mach=k6-2 -o3” kde-full urpms would then sort out the dependencies required for a full install of kde the kde packages build them in the correct order with the CFLAGS and CXXFLAGS set to the –flags option and install them setting up kdm or mdkdm. I'd also like to be able to do the same with gcc so “ urpms –flags=xxx gcc” 2)Next I'd propose the development of an app called some thing like bugdrake. It would be a Wizard/Gui client side front end for Bugzilla. It would ask for specific info that users often forget to add to their bug reports, if it was a hardware problem it would ask if it could scan the machine and collect info that would be of use in hunting down the bug. As well as checking to find out what version of Mandrake the user was using eg mdk9.0, mdk9.1RC1, mdk9.0/cooker hybrid etc and if the users had selected a specific package for the bug report check it and it's dependence's to find out what version they were and check that the user hadn't replaced them with non standard versions. It would then gather all the info and submit it to bugzilla.Possibly it could check for any simliar bug reports using some sort of alogarithim and show any thing that showed up as being similar to the user and asking them if it was the same bug. In which case it would mark it as a duplicate and add it as a comment to the end of the previous bug report to supply additional info. This should/would improve the quality and detail of most bug reports which I think most people here would agree would be very usefull! 3)The final suggestion I have is for the creation of an App called something like drakecooker or cookerdrake. This would be a program for helping with cooker testing. A gui or commandline interface which could control updateing the cooker installation. Allowing users to choose when and what parts of cooker they wanted to update and set up cron jobs to do it. - -It would report/list what packages had been updated after runing the update cooker command and list the changes made to them (scan the changelog in the spec file). - - List requests for moreinfo on bugs and specific requests for testing of new or updated packages. It would be closely tied to bugdrake allowing easy bug reporting etc. - -report bugs in areas of interest. So you could tell it you wanted to mainly test Multimedia pacakges it would then list new, needinfo and unresolved bugs from the mulitmedia packages section that you could have a look at, test etc. - - and have a package/cvs upload front end for uploading changes or patches. I think the creation of such apps would help the cooker community in it's efforts to improve Mandrake Linux and crush the ever present stream of bugs. I'd personally give the bugdrake app ago my self if my programing skills were up with it but they're certainly not (abit of java and tiny bit of perl and pascal)! What do you think? Chad - -- "If you want to travel around the world and be invited to speak at a lot of different places, just write a Unix operating system." (By Linus Torvalds) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+eDr0IzniS8MsaSYRAp7FAJ0ZmyPZXok4Qh7dMIqO58WTT5TdtwCfU1cL RJWYYtkcW94rlPPe9kaxiRM= =Zor0 -----END PGP SIGNATURE-----
