From c732ea1fdca275f8869f072d772c42c782ba228f Mon Sep 17 00:00:00 2001 From: Marius Mauch Date: Sat, 6 Oct 2007 12:04:28 +0000 Subject: default set configuration, should probably go into /usr/share/portage svn path=/main/trunk/; revision=7977 --- cnf/sets.conf | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 cnf/sets.conf (limited to 'cnf') diff --git a/cnf/sets.conf b/cnf/sets.conf new file mode 100644 index 000000000..8f7852b85 --- /dev/null +++ b/cnf/sets.conf @@ -0,0 +1,34 @@ +# WARNING: default set configuration, DO NOT CHANGE. +# If you want to change anything redefine the relevant section in +# /etc/portage/sets.conf. Any changes to this file will be lost on the next +# portage update, and configuration errors here might upset portage in +# unexpected ways. + +# Not much that could be changed for world, so better leave it alone +[world] +class = portage.sets.files.WorldSet + +# Same as for world, though later portage versions might use a different class +[system] +class = portage.sets.profiles.PackagesSystemSet + +# For security there are multiple classes available, but differences are +# rather small (normally there should be no visible difference): +# - AffectedSet: include all GLSAs that cover a vulnerable package +# - NewAffectedSet: include all GLSAs that cover a vulnerable package and +# haven't been applied previously +# - NewGlsaSet: include all GLSAs that haven't been applied +# - SecuritySet: include all GLSAs +[security] +class = portage.sets.security.NewAffectedSet + +# Again, not much to change here, though people might prefer a different name +[everything] +class = portage.sets.dbapi.EverythingSet + +# The following treats all files in /etc/portage/sets as a package set called +# 'sets/$filename'. +[usersets] +class = portage.sets.files.StaticFileSet +multiset = true +directory = /etc/portage/sets -- cgit v1.2.3-1-g7c22