I'll follow. Let me start with saying that I want to see smart and yum succeed. I look forward to the day that there is one format package repo format for suse operational.
Op zaterdag 7 januari 2006 01:54, schreef Pascal Bleser: > So about the question what can smart do that yast2's package manager > doesn't. > There is still much room for improvements, no question about that, but what > Christoph meant and what I'd also like to ask: please test it and file bug > reports. And if you'd like to contribute in other ways: coding on the > project, translating locale messages, writing documentation. What does not work: are urls with login and passwords, like: ftp://login:[EMAIL PROTECTED]/dir This works with yum Why does smart not read the /etc/yum.repos.d directory? I now have to define the repositories twice :( Smart is not integrated with suse... I mean the "OK" button is at the right side while suse (kde) has it left... (nothing will be done about it, I know). There is a field labelled alias and another one name (when adding a channel). I think the name field should be labelled "description". If that would happen the alias field could be labelled "name"... > So, what's so nice about Smart. > * mirrors > - mirrors are managed globally, for every single operation, because you > just define URL mappings (e.g. > "http://ftp.gwdg.de/pub/opensuse/distribution/SL-10.0-OSS"; -> > "http://ftp.belnet.be/packages/opensuse/distribution/SL-10.0-OSS";), that's > it, it will apply for every file retrieval because it's managed by a > central component Is there a central directory that shows which repositories are available? Something like the /etc/yum.repos.d directory but than on a central server. (Perhaps start on wiki page)? packman has a mirrorlist file, I have a just created a repodata file, there is one for kolab, but where can these be registered? How do we know what is available, without searching the whole internet? Perhaps Eberhard can make a directory that hold links to all the repodata directories on his server? > But it has already proven to be very solid and consistent in terms of > package management and dependency handling (especially 0.41 that sorts out > a lot of bugs that happened on SUSE Linux < 10.1 because of an older RPM > version). command line tool yummie :) Heh, why is the /etc/yum.repos.d so empty when it is installed?? Why does it not come preconfigured with information for base, security, and all the other goodies (of course they could all be disabled). > http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=/System/smart It was very easy to install with apt :) Do you have a yum repodata directory? Why is yum not able to find yast2-tv? hp100:/etc/yum.repos.d # time apt search yast2-tv yast2-tv - YaST2 - TV Configuration real 0m5.794s user 0m2.864s sys 0m0.940s hp100:/etc/yum.repos.d # time yum search yast2-tv Searching Packages: Setting up repositories suser-rbos 100% |=========================| 951 B 00:00 base 100% |=========================| 951 B 00:00 packman 100% |=========================| 951 B 00:00 kolab 100% |=========================| 951 B 00:00 Reading repository metadata in from local files No Matches found real 0m19.979s user 0m12.705s sys 0m1.284s What about the rpmkey rpms? Will they be supported? I saw that each rpmkey file has to be configured in the /etc/yum.repos.d/* files? Why is it that way, why should they be configured in those repository files? Sofar my ramblings. it nice to see that smart works now (this was not the case when a I tested version 0.2 (or something like that) some years ago) -- Richard Bos Without a home the journey is endless --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
