someone_stole_my_name.portage_cfg

portage-cfg

This is a tool to manage various Portage configuration files.

Role Variables

• portage_ansible_managed_filename: When dealing with directory paths like /etc/portage/package.accept_keywords, a file with this name will be created in the same path to include the requested line. [Default: ansible_managed]

• portage_accept_keywords: A list of keywords that you want to accept. Example:

  portage_accept_keywords:
    - atom: app-admin/ansible
      keyword: ~amd64
      # If you specify `name`, a file with that name will be created in the `portage.accept_keywords` directory.
      name: some_filename
  

• portage_accept_license: A list of licenses that you want to accept. Example:

  portage_accept_license:
    - atom: app-editors/visual-studio-code
      license: MS-vscode-EULA license
      # If you specify `name`, a file with that name will be created in the `portage.accept_keywords` directory.
      name: some_filename
  

• portage_unmask: A list of entries to add to the package.unmask file or to a file in that directory.

• portage_mask: A list of entries to add to the package.mask file or to a file in that directory.

• portage_sets: A list of sets to create. Each set is also added to world_sets. Example:

  portage_sets:
    - name: fonts
      packages:
        - media-fonts/corefonts
  

• portage_package_use: A list of uses. Each entry creates a new file under /etc/portage/package.use with its name. Example:

  portage_package_use:
    - name: ansible
      uses:
        - use: dev-python/ipython -qt5
          comments:
            - This pulls in several dependencies
  

• portage_world: A list of packages to add to the world file.

• portage_make: A list of custom lines to add to make.conf. Example:

  portage_make:
    - name: LINGUAS
      value:
        - en
        - es
  

License

This project is licensed under the BSD license.