Am Sonntag, 6. August 2006 15:05 schrieb Andreas Hanke:
createrepo is not a solution at all IMHO. Using createrepo for such a basic functionality as installing packages from local directories doesn't sound like a good idea to me because it means making kdebase3-SuSE (and hence KDE) depend on a development tool (createrepo is a development tool in my eyes).
Hm, it's more a matter of organization. Note that you run a tool like createrepo once after modification of a repo, and it's going to be usable for all your systems. (computers tend to breed nowadays) Sure, yast could do that by itself, and even on every start, but that would reduce user experience drastically for some setups (My local repo has about 500 packages..) Maybe a daemon, based on inotify, that triggers the rebuild everytime the repo changes, would be a smart solution to this problem..
Regarding your specific proposal of somehow integrating createrepo into the YaST GUI: Well, if there is no other solution going to be in place for 10.2, doing that might be better than not doing anything because installing RPMs from local directories is a desperately needed feature. But the approach looks strange. Actually I proposed it myself some time ago, but I don't like it.
As a quick hack for now, you can create a shell script like this:
#!/bin/sh createrepo /usr/src/packages/RPMS /sbin/yast2 sw_single
Please check the -c option, e.g. createrepo -qc repocache .. I've a patch pending to createrepo to speed this up considerably again, if the repo didn't change between invocations. Just ask.. Pete --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org