SHARE
TWEET

Untitled

a guest Jun 11th, 2017 190 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. [MAIN]
  2. #-----------------------------------------------------------
  3. # Defines the directory where overlays should be installed
  4.  
  5. storage   : /var/lib/layman
  6.  
  7. #-----------------------------------------------------------
  8. # Remote overlay lists will be stored here
  9. # layman will append _md5(url).xml to each filename
  10.  
  11. cache     : %(storage)s/cache
  12.  
  13. #-----------------------------------------------------------
  14. # The list of locally installed overlays
  15.  
  16. installed: %(storage)s/installed.xml
  17.  
  18. #-----------------------------------------------------------
  19. # Prompt the user if they are installing unofficial overlays
  20.  
  21. check_official : Yes
  22.  
  23. # This has been renamed from the following
  24. # old name  : value use it for updating to new one above
  25. # local_list: %(storage)s/overlays.xml
  26. # either rename the overlays.xml file to installed.xml
  27. # or edit the value above to the current name of your
  28. # installed overlay(s) file.
  29.  
  30. ##### Repo Config Options #####
  31. #-----------------------------------------------------------
  32. # Defines whether or not a repos.conf or make.conf file is
  33. # required for the repository control group. Set to No for
  34. # non-package manager involved repository control. For normal
  35. # portage overlay use and function, this needs to be set to
  36. # Yes. If yes, it requires at least one conf_type to be set.
  37.  
  38. require_repoconfig : Yes
  39.  
  40. #-----------------------------------------------------------
  41. # Path to the make.conf file that should be modified by
  42. # layman
  43.  
  44. make_conf : %(storage)s/make.conf
  45.  
  46. #-----------------------------------------------------------
  47. # Path to the repos.conf file that should be modified by
  48. # layman
  49.  
  50. repos_conf : /etc/portage/repos.conf/layman.conf
  51.  
  52. #-----------------------------------------------------------
  53. # Defines whether or not auto_sync will be set to "yes" or
  54. # "no" in your repos.conf config. Ultimately deciding whether
  55. # or not the portage sync plug-in will automatically sync your
  56. # layman overlays.
  57.  
  58. auto_sync : Yes
  59.  
  60. #-----------------------------------------------------------
  61. # Repository config types used by layman
  62. # (repos.conf, make.conf)
  63.  
  64. conf_type : repos.conf
  65.  
  66. #-----------------------------------------------------------
  67.  
  68. #### Database Config Options #### #### COMING SOON ####
  69. #-----------------------------------------------------------
  70. # Database types used by layman, only one should be specified.
  71. # (xml, json, sqlite)
  72. #db_type : xml
  73.  
  74. #-----------------------------------------------------------
  75.  
  76. #-----------------------------------------------------------
  77. # Protocols used by layman when adding overlays or updating
  78. # their URLs.
  79. # ex.) protocol_filter : git, http, https, etc,...
  80. # protocol_filter :
  81.  
  82. #-----------------------------------------------------------
  83. # URLs of the remote lists of overlays (one per line) or
  84. # local overlay definitions
  85. #
  86. #overlays  : http://www.gentoo.org/proj/en/overlays/repositories.xml
  87. #            http://dev.gentoo.org/~wrobel/layman/global-overlays.xml
  88. #            http://mydomain.org/my-layman-list.xml
  89. #            file:///var/lib/layman/my-list.xml
  90. #
  91. #### GPG signed lists #### COMING SOON TO A DOWNLOAD SITE NEAR YOU #####
  92. #
  93. #  gpg_signed_lists :
  94. #       These can be clearsigned or signed (compressed) overlay lists
  95. #       Each url will be one complete file to download, verify, decrypt.
  96. #       layman will automatically verify and decrypt the list before saving
  97. #       One url per line, indented
  98. #
  99. #   e.g.:
  100. #    gpg_signed_lists :
  101. #        http://someserver.somewhere.com/someoverlays.xml.asc
  102. #
  103. gpg_signed_lists :
  104.  
  105. #
  106. # gpg_detached_lists:
  107. #       These url's involve downloading 2 files
  108. #       The first url listed will be the overlays xml list.
  109. #       The second url will be the detached signature file
  110. #           with one of {.gpg, .asc, .sig} extension
  111. #       Both url's must be on the same line space separated and indented
  112. #
  113. #   e.g.:
  114. #    gpg_detached_lists :
  115. #        http://distfiles.gentoo.org/overlays.xml http://distfiles.gentoo.org/overlays.xml.asc
  116. #        http://someserver.somewhere.com/someoverlays.xml http://someserver.somewhere.com/someoverlays.xml.gpg
  117.  
  118. gpg_detached_lists :
  119. #    https://api.gentoo.org/overlays/repositories.xml https://api.gentoo.org/overlays/repositories.xml.asc
  120.  
  121. #  original unsigned lists and definitions
  122. #  one url per line, indented
  123.  
  124. overlays  :
  125.     https://gitweb.gentoo.org/report/repos.git/plain/repositories.xml
  126.     https://api.gentoo.org/overlays/repositories.xml
  127.  
  128.  
  129. #-----------------------------------------------------------
  130. # The directory to scan for xml overlay definition files to include
  131. # in the list of available overlays.  They are automatically added to the
  132. # "overlays" parameter above.  Use either method, but do not add the same
  133. # definition in both.
  134. #
  135.  
  136. #overlay_defs : /etc/layman/overlays
  137.  
  138. #-----------------------------------------------------------
  139. # Proxy support
  140. # If unset, layman will use the http_proxy/https_proxy environment variable.
  141. #
  142. #http_proxy  : http://[user:pass@]www.my-proxy.org:3128
  143. #https_proxy : https://[user:pass@]www.my-proxy.org:3128
  144.  
  145. #-----------------------------------------------------------
  146. # Strict checking of overlay definitions
  147. #
  148. # The nocheck option is a bit confusing, for historical reasons.
  149. # Hopefully this description eases the double negation trouble:
  150. #
  151. # nocheck : yes
  152. # - Accepts complete overlay entries without warnings
  153. # - Lists overlays of type foo (say Git) even with no foo installed
  154. #
  155. # nocheck : no
  156. # - Checks overlay entries for missing description or contact
  157. #     information and issue warnings as needed
  158. # - Hides overlays of type foo (say Git) if foo not not installed
  159. #
  160. nocheck  : yes
  161.  
  162. #-----------------------------------------------------------
  163. # Umask settings
  164. #
  165. # layman should usually work with a umask of 0022. You should
  166. # only change this setting if you are absolutely certain that
  167. # you know what you are doing.
  168. #
  169. #umask  : 0022
  170.  
  171. #-----------------------------------------------------------
  172. # News reporting settings
  173. #
  174. # This is for when layman is adding/syncing overlays.
  175. # It is required  for GLEP 42.
  176. # Currently there are 3 possible values:
  177. #   portage, pkgcore, custom
  178. #
  179. # portage:  uses portage to report news only from overlay(s) in
  180. #           versions >=2.2.0_alpha72 or >=2.1.10.32
  181. #           or all repositories (including gentoo) for older portage versions.
  182. # pkgcore:  does not yet support glep 42, no news is reported
  183. # custom:   requires that you provide a suitable python function
  184. #           to 'custom_news_func' using the api's config.set_option()
  185. #           or define the python package to import it from in custom_news_pkg
  186.  
  187. news_reporter: portage
  188.  
  189. #-----------------------------------------------------------
  190. # News reporting custom function setting
  191. #
  192. # the pkg name that contains the layman_news_function()
  193. # for it to import and use.  It must be found in PYTHONPATH
  194.  
  195. #custom_news_pkg :
  196.  
  197. #-----------------------------------------------------------
  198. # Command overrides
  199. #
  200. # You can have commands point to either a binary at a different
  201. # location, e.g.
  202. #
  203. #   /home/you/local/bin/git
  204. #
  205. # or just the command, e.g.
  206. #
  207. #   git
  208. #
  209. # to use PATH-based resolution of the binary to call.
  210. #
  211. #bzr_command        : /usr/bin/bzr
  212. #cvs_command        : /usr/bin/cvs
  213. #darcs_command      : /usr/bin/darcs
  214. #git_command        : /usr/bin/git
  215. #mercurial_command  : /usr/bin/hg
  216. #rsync_command      : /usr/bin/rsync
  217. #left intentionally blank since squashfs only needs to
  218. #mount the squashfs image.
  219. #squashfs-command   :
  220. #svn_command        : /usr/bin/svn
  221. #tar_command        : /bin/tar
  222. #g-sorcery_command  : /usr/bin/g-sorcery
  223.  
  224.  
  225. #-----------------------------------------------------------
  226. # Command additional options
  227. #
  228. # These commnad options will be added to the above commands
  229. # when the overlay is added or synced.
  230. # Use spaces to separate command line arguments
  231. #
  232. #    note: there are some options hardcoded in the backend
  233. #          scripts already.  All VCS types listed here are
  234. #          for general consistency.  Options may not be available
  235. #          or recommended for all VCS types and/or add/sync operations.
  236. #          Any options defined here are deemed:
  237. #                "Use at your own risk"
  238. #          and are not supported.
  239. #
  240. #  eg:
  241. #     svn_addopts : --config-option=config:miscellany:use-commit-times=yes
  242. #
  243.  
  244. #bzr_addopts :
  245. #bzr_syncopts :
  246. #cvs_addopts :
  247. #cvs_syncopts :
  248. #darcs_addopts :
  249. #darcs_syncopts :
  250. #git_addopts :
  251. #git_syncopts :
  252. #mercurial_addopts :
  253. #mercurial_syncopts :
  254. #rsync_syncopts :
  255. #svn_addopts :
  256. #svn_syncopts :
  257. #g-common_generateopts :
  258. #g-common_syncopts :
  259. #g-sorcery_generateopts :
  260. #g-sorcery_syncopts :
  261.  
  262.  
  263. #-----------------------------------------------------------
  264. # Per VCS Post Sync/Add hooks
  265. #
  266. #  The listed commands will be run after every add/sync operation.
  267. #  All on one line  If the repo path is needed, use a %cwd= in
  268. #  where you want the path substituted in.  It will be detected
  269. #  and replaced with the correct path.
  270. #
  271. #  eg: git_postsync : git-set-file-times
  272. #  eg: git_postsync : git-set-file-times %cwd=
  273. #  eg: git_postsync : git-set-file-times path=%cwd=
  274. #
  275. #bzr_postsync :
  276. #cvs_postsync :
  277. #darcs_postsync :
  278. #git_postsync :
  279. #mercurial_postsync :
  280. #rsync_postsync :
  281. #svn_postsync :
  282. #tar_postsync :
  283. #g-common_postsync :
  284. #g-sorcery_postsync :
  285.  
  286.  
  287. #-----------------------------------------------------------
  288. # Layman user info
  289. #
  290. #  The user name and email to use when adding new repos
  291. #
  292. #git_user  : layman
  293. #git_email : layman@localhost
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
Top