On Thu, Aug 28, 2008 at 03:16:20 +0200, Bernhard Walle wrote:
* Peter Poeml [2008-08-28 15:05]:
And of course the fact that it is tried and tested
But not with openSUSE. While I'm normally for diversity, I think one
You may want to use a yum package that is known to work, not just what
happens to be in Factory at a given time. YMMV with that.
I can assure you it has been working very well during the last years.
As I indicated, I care more about SLES, and I use my own build of yum
(that I can rely on).
package manager is enough for the core distribution.
distributions ship "foreign" package managers?
From a build service perspective, where we offer packages for other
distributions, we have a need to be compatible in a way that clients
used on other distributions (like yum, smart, whatever) can be used to
install and update software from the build service.
Thus, I consider it an advantage if we know that it works, and this
already is a reason to have yum on our distribution.
You need to know that the build service uses repo-md metadata, which is
the yum-style metadata which zypper happens to understand _also_.
In the past, there have been discussions on and off whether to introduce
features in our metadata that would make them incompatible with yum,
smart and other package managers. I consider it the right thing that we
could avoid that. Thus, I'm all for diversity in this regard. It is a
strength of us (and of the build service in particular) that you can use
it from different distributions, with various package managers, because
our metadata stays on common ground.
The build service actually uses createrepo, the companion tool of yum to
create its metadata. I believe it is very good for us to be based on a
BTW, when looking in the download.opensuse.org
logs, then yum is the
second most used package manager after libzypp-based clients.
"WARNING: This bug is visible to non-employees. Please be respectful!"
SUSE LINUX Products GmbH
Research & Development