Software management in future openSuse 10.3: no zmd anymore

openSuse changed the software management tools every time the last two releases. The upcoming release 10.3 will see another change: zmd will vanish.

According to Andreas Jaeger zmd will be dropped because it will be developed for the enterprise versions only – openSuse software management will be left to libzypp and Yast itself:

openSUSE is focusing on native software management by using YaST and
libzypp, the package management library.

ZENworks Linux Management is Novell’s solution for enterprise-class
resource management for desktops and servers. ZENworks components are
fully available and supported for SUSE Linux Enterprise based products
and not longer part of the openSUSE distribution.

From my perspective this is not as bad as it sounds since the software management on openSuse was a bit unclear (but brought me many readers 😉 ). This move to drop zmd will leave openSuse with Yast/zypp alone and will therefore concentrate on one single solution – an attempt which totally makes sense because it will help the user.
But of course you can still use apt or yum if you prefer: they all use the same repository format, so no problems there.

Keep in mind that this news is about a still in development distribution – it might change again.


5 thoughts on “Software management in future openSuse 10.3: no zmd anymore”

  1. Sorry, but how would you use apt if there are no apt repositories any longer? I’d like to know that. Thanks.

  2. Hi Gandolfo, apt4rpm does not need specific repository formats anymore. In fact, it can use the same repository format all other rpm based software management systems use as well: XML package metadata (only urpmi uses something else, I guess).
    Some more info can be found in this post: apt4rpm and Fedora Core

  3. First, make sure that you have an apt-version which supports the new metadata format, like 0.5.15lorg3.1 or newer (for example from ). The apt-version originally shipped with OpenSuse 10.2 was too old, I’m not sure if there was an update through regular channels!

    After that, configure your sources.list just like that:
    repomd suse

    The only difference is the repo type at the beginning.
    If the above mentioned package does not come along with a pre-configured sources.list you might want to check the wiki articles.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s