From 7da333dc63eaa2b3baa0cafebf6a3a6bc235e2d6 Mon Sep 17 00:00:00 2001
From: Ciaran McCreesh The The As well as the general keys supported for all repositories, the following keys have meaning
-for ebuild and exheres Repository Formats
+ Repository Format
-ebuild
repository format is used on Gentoo and derived distributions for repositories containing
-ebuilds. The exheres
repository format is used on Exherbo for repositories containing exheres packages.
-Except where noted, all options described below are common to both formats.e
repository format is used on Gentoo and derived distributions for repositories containing ebuilds,
+and on Exherbo for repositories containing exheres packages. Except where noted, all options described below are common
+to both distributions.ebuild
and exheres
format repositories:e
format repositories:
location
master_repository
Exheres
format repositories describe their own masters, so this option does not apply to them.profiles
ebuild
and exheres
format repositories:
eclassdirs
ECLASSDIR
, but eclasses in later directories have priority. Optional, and not used by
- exheres
format repositories.distdir
format
ebuild
, vdb
and installed_unpackaged
. Mandatory.e
, vdb
and installed_unpackaged
. Mandatory.
importance
Paludis makes use of scripts called 'syncers' to perform certain sync actions (e.g. handling paludis
- --sync
for ebuild format repositories). Some syncers support additional options that can be set via the
+ --sync for e format repositories). Some syncers support additional options that can be set via the
sync_options
repository configuration key. Syncers can be added for additional protocols (for example, if
you need to use a repository that uses a weird version control system), and built-in syncers can be replaced (for
example, if you want to use a non-standard program).
Don't confuse the profiles/
directory with the profiles
- =
setting for ebuild format repositories. The special files
+ = setting for e format repositories. The special files
immediately under profiles/
, such as
profiles/thirdpartymirrors
, profiles/use.desc
and profiles/package.mask
, are specific to the repository and not
@@ -25,7 +25,7 @@ peanut gallery, repositories are required to be uniquely identifiable. The
identifier must remain consistent even if a repository is moved, either locally
or remotely, and thus must be independent of user configuration.
For ebuild format repositories, this is controlled by the profiles/repo_name
+
For e format repositories, this is controlled by the profiles/repo_name
file. It should contain a single string with no whitespace or funny characters.
For many repositories, this has already been created for you; for some overlays,
probably including your local overlay if you have one, the file is not yet
diff --git a/doc/overview/gettingstarted.html.part b/doc/overview/gettingstarted.html.part
index cc3ee531c..899c13161 100644
--- a/doc/overview/gettingstarted.html.part
+++ b/doc/overview/gettingstarted.html.part
@@ -200,7 +200,7 @@ reasons, it is strongly recommended that the filename used matches the name of t
location = /usr/portage
sync = rsync://rsync.europe.gentoo.org/gentoo-portage/
profiles = ${location}/profiles/default-linux/x86/2007.1
-format = ebuild
+format = e
names_cache = (see below)
@@ -259,7 +259,7 @@ location = /var/paludis/repositories/paludis-overlay/
sync = git://git.pioto.org/paludis-overlay.git
names_cache = (as above)
write_cache = (see below)
-format = ebuild
+format = e
If write_cache =
is set to (for example) /var/cache/paludis/metadata
, Paludis will write
@@ -291,7 +291,7 @@ config.