[HOWTO] Installation von smart

smart
1. <programming> Said of a program that does the {Right Thing} in a wide variety of complicated circumstances. (...)

"kernel" should be one of the packages marked with a "multi-version" tag. You can check this by running this:

$ smart flag --show multi-version
multi-version
    kernel
    kernel-doc
    kernel-smp

Or through Edit->Flags in the GUI, where you can also add your own multi-version packages. (or using smart flag --set multi-version <package> in the command line)

When you install a new kernel, Smart may display a dialog saying the new package "upgrades" your old packages. But unless those packages have as their icon they won't be removed. Installation of new multi-version packages does not imply the previous packages will be removed, even if they satisfy the requirements for an "upgrade" operation.

In the GUI, go to Edit->Mirrors, click "New" and set your Origin URL and Mirror URL. Most likely you will be using whatever it is that you used as Base URLs for your repositories as Origin URLs. You may add as many Mirror URLs to an Origin URL as you wish, and you shouldn't worry too much about slow mirrors and mirrors going out of date. Smart automatically handles bad/inefficient mirrors and avoids them in the future.

All channels are created equal. Smart will attempt to upgrade to the newest package. If you wish to override that, you may assign priorities to channels and packages. To configure your channel priorities, go to Edit->Channels, pick a channel, click "Properties" and set a value in "Priority". Or you can use the CLI equivalent:

# smart channel --set <mychannel> priority=10

Highest numbers imply higher priority.

If you want more granularity, you can define priorities for individual packages in individual channels. To do that, right-click the package and select "Priority". This setting overrides channel priorities. Also, on the CLI you can:

# smart priority --set <packagename> <mychannel> 10
# smart priority --set <otherpackage> <otherchannel> -- -20

As you can see, it's possible to use negative priorities, given that they should be preceded by '--' (two dashes), otherwise they will be interpreted as command line options. Negative priorities are no different than positive ones, they it's just a matter of taste to use them or not.

If you are familiar with packaging, think of Priorities as user-defined "epochs".

While priorities are powerful, they are also dangerous. A channel with higher priority will always have precedence over other channels, including your local package database. It is easy to get in a situation where your system has to downgrade packages because a remote, out-of-date channel has higher priority than your installed packages. If all you want to do is be sure that your vendor's packages are preferred over third-party packages, it may be easier and safer to lower the third-party channel to a priority below zero (zero being the default) rather than increasing other priorities.

(In fact, priorities are more complicated than this, and in some situations Smart may choose a package in a channel with a lower priority. Priorities influence the weight each possible transaction is given, so it does make a difference whether a priority is set to -1, -5 or -100. The exact way this works is, for now, undocumented.)

Right-click them in the GUI and choose "Lock this version" or "Lock all versions", as you wish. Or use smart flag --set lock <package>. Notice that you may lock even packages that are not currently installed. In this case, Smart will never install the locked package.

RPM System Database (locally installed packages)
APT repositories for .rpm
RPM-MD (used by YUM)
Red Carpet (used by Ximian/Novell)
RPM Header List (used by RedHat and Conectiva installation CDs, probably others)
RPM Directory (a directory with a bunch of RPMs in it, no indexing required)
URPMI (used by Mandriva)

DEB System Database (locally installed packages)
APT repositories for .deb
DEB Directory (a directory with a bunch of DEBs in it, no indexing required)

Slackware installed packages database
Slackware repositories

up2date (used by RedHat/Fedora)
Conectiva-style mirror description formats

Exec=kdesu -c "/usr/bin/smart --gui"

[Desktop Entry]
X-SuSE-translate=true
Categories=System;PackageManager;System;
Encoding=UTF-8
MultipleArgs=false
Terminal=false
Icon=smart
Exec=smart --gui
Type=Application
StartupNotify=true
Name=Smart Package Manager
GenericName=Package Manager
Comment=Install packages from various sources
X-KDE-SubstituteUID=true
X-KDE-Username=root
X-SuSE-translate=true

smart install smart-ksmarttray

smart config --set rpm-check-signature=true

smart config --set remove-packages=false

smart update entspricht apt-get update

smart install entspricht apt-get install <packetname>

smart upgrade entspricht apt-get upgrade

smart --gui startet die GUI für smart, ähnlich zu bedienen wie synaptic

smart remove deinstalliert Pakete

smart channel --help  weitere "Channels" zu smart hinzuzufügen, bitte die sehr ausführliche Hilfe lesen

smart channel --add /media/dvd  SuSE-DVD zu den channels hinzufügen

[oc2pus-apt]
name = suser-oc2pus 3rd party package repository for SUSE Linux on ftp.gwdg.de
baseurl = http://ftp4.gwdg.de/pub/linux/suse/apt/SuSE/9.3-i386
type = apt-rpm
components = suser-oc2pus

#!/bin/bash
if [ -e smart-cmd.txt ]; then
	rm -f smart-cmd.txt
fi

smart --help >> smart-cmd.txt
echo "----------------" >> smart-cmd.txt
echo "----------------" >> smart-cmd.txt

for i in update install reinstall upgrade remove check fix download \
	search query info stats \
	channel priority mirror flag; do
	smart  $i --help >> smart-cmd.txt
	echo "----------------" >> smart-cmd.txt
	echo "----------------" >> smart-cmd.txt
done