system, update them and merge the updated ones.
What's the point in creating such tool when portage-2.2 comes with builtin
indeed have changed and need to be rebuilt.
1) parallel updates support
As you might have already noticed, fetching from remote repositories suffers
whenever you abort the merge or update process.
In most cases, s-l-r needs to be run as root. This has serious security impli-
cations, which the scripts tries to overcome dropping the privileges whenever
Moreover, in the latter case s-l-r can be run directly by the 'portage' user.
Apart from being called directly, smart-live-rebuild provides a package set
for portage-2.2, called SmartLiveRebuild.sets.SmartLiveRebuildSet. Please take
a look at 'sets.conf.example' file for a use example.
Various options to smart-live-rebuild may be set in a configuration file too.
The path to that file can be specified as '--config-file' (or '-c'), and
the default one is '/etc/portage/smart-live-rebuild.conf'.
ConfigParser python class (i.e. true/false/yes/no/on/off). The 'type' list
has to be comma-separated.
Example config file may look like:
+xample config file may look like:
Additionally, configuration files can be chained. To do so, just specify path
to the next configuration file as 'config_file'. Please notice though that
replace values set by yours.
+<!-- vim:se syn=markdown : -->