Browse Source

add missing options

master
belliash 8 years ago
parent
commit
2aff5ad0bd
1 changed files with 22 additions and 0 deletions
  1. +22
    -0
      config/ezsync.conf

+ 22
- 0
config/ezsync.conf View File

@ -7,3 +7,25 @@
# NOTE: Not every protocol can be used for building Portage tree!
PORTAGE_BUILD=( "build-portage" "git" "git://git.mydomain.org/build-portage.git" "my_branch" )
PORTAGE_MAINLINE=( "mainline-portage" "rsync" "rsync://rsync.mydomain.org/mainline-portage" "N/A" )
# These defines overlays that may be used later in a Portage synchronization process.
# Ordered listparameters are:
# overlay name = the overlay name (eg. regen2-overlay)
# protocol used = protocol being used by repository (git, rsync, svn)
# remote address = the remote repository address to clone from and send commits to
# optional branch = in a non-bare repository, this is the branch that will be fetched
# files to copy = comma separated list of packages to merge, or ALL to merge every
# existen packages, eclasses and licenses
# files to skip = comma separated list of packages to skip while merging; useful
# when copying everything but specified here files. Nothing will be
# skipped when set to NONE or N/A
# overwrite mask = tells whether EzBuild should overwrite already existen files or not
# NOTE: Not every protocol can be used for building Overlay!
OVERLAY_BUILD=( "build-overlay" "git" "git://git.mydomain.org/build-overlay.git" "master" "ALL" "NONE" 1 )
OVERLAY_TEMP=( "temp-overlay" "svn" "svn://svn.mydomain.org/temp-overlay" "N/A" "ALL" "my-cat1/package1,my-cat2/package2" 0 )
# Directives set overlays that are going to be merged into build overlay or Portage tree.
# To avoid any unexpected situations, the overlays need to be defined somewhere above in
# this file. Otherwise EzBuild will be unable to fetch and merge them at a later point.
MERGED_OVERLAY=( OVERLAY_TEMP )
MERGED_PORTAGE=( OVERLAY_BUILD )

Loading…
Cancel
Save