importare(1)
Name
importare - The Paludis unpackaged package installer
Synopsis
importare [ --install ] [ --location path/ ] category/package [ version ] [ slot ]
Description
importare can be used to manage packages where no real package file is available. It treats the contents of a named directory as being the content of the package, and uses a dummy package name provided on the command line to do the install. Safe merge, unmerge, upgrade and replace support is provided, as is content tracking for installed files.
Options
Actions
Selects which basic action to perform. Exactly one action should be specified.
- -i, --install
- Install one or more packages (default)
- -V, --version
- Display program version
- -h, --help
- Display program help
General options
Options which are relevant for most or all actions.
- --log-level
- Specify the log level
- debug
- Show debug output (noisy)
- qa
- Show QA messages and warnings only (default)
- warning
- Show warnings only
- silent
- Suppress all log messages (UNSAFE)
- --no-colour
- Do not use colour
- --no-color
- Alias for --no-colour
- --force-colour
- Force the use of colour
- --force-color
- Alias for --force-colour
- -E, --environment
- Environment specification (class:suffix, both parts optional)
- --compact (--no-compact)
- Display output using one line per entry
Source options
Options affecting the source image
- -l, --location
- Location of source image (default: current directory)
- -u, --install-under
- Install under a given directory (default: /)
- -r, --rewrite-ids-over-to-root
- Change any UID or GID over this value to 0 (-1 disables, default)
Metadata options
Options affecting generated metadata
- -D, --description
- Specify a package description
- -B, --build-dependency
- Specify a build dependency
- -R, --run-dependency
- Specify a run dependency
- -P, --preserve-metadata (--no-preserve-metadata)
- If replacing a package, copy its description and dependencies
Install options
Options which are relevant for --install
- -p, --pretend
- Pretend only
- -d, --destinations
- Use specified destinations instead of defaults
- -1, --preserve-world (--no-preserve-world)
- Don't modify the world file
- --show-reasons
- Show why packages are being (un)installed
- none
- Don't show any information
- summary
- Show a summary (default)
- full
- Show full output (can be very verbose)
- --show-use-descriptions
- Show descriptions of USE flags
- none
- Don't show any descriptions
- new
- Show for new use flags
- changed
- Show for new and changed flags (default)
- all
- Show for all flags
- --show-package-descriptions
- Show package descriptions
- none
- Don't show any descriptions
- new
- Show descriptions for new packages (default)
- all
- Show descriptions for all packages
- --continue-on-failure
- Whether to continue after a fetch or install error
- if-fetch-only
- If fetching only (default)
- never
- Never
- if-satisfied
- If remaining packages' dependencies are satisfied
- if-independent
- If independent of failed and skipped packages
- always
- Always (UNSAFE)
- --skip-phase
- Skip phases with a given name (e.g. init, preinst, unpack, merge, strip). Dangerous.
- --abort-at-phase
- Abort when a phase with a given name is encountered.
- --skip-until-phase
- Skip all phases until a phase with a given name is encountered. Dangerous.
- --change-phases-for
- Control to which package or packages options --skip-phase, --abort-at-phase and --skip-until-phase apply.
- all
- All packages (default)
- first
- Only the first package on the list
- last
- Only the last package on the list
DepList behaviour
Modify dependency list generation behaviour. Use with caution.
- --dl-reinstall
- When to reinstall packages
- never
- Never (default)
- always
- Always
- if-use-changed
- If USE flags have changed
- --dl-reinstall-scm
- When to reinstall scm packages
- never
- Never (default)
- always
- Always
- daily
- If they are over a day old
- weekly
- If they are over a week old
- --dl-upgrade
- When to upgrade packages
- always
- Always (default)
- as-needed
- As needed
- --dl-new-slots
- When to pull in new slots (works with --dl-upgrade)
- always
- Always (default)
- as-needed
- As needed
- --dl-downgrade
- When to downgrade packages
- as-needed
- As needed
- warning
- As needed, but warn when doing so (default)
- error
- Downgrades should be treated as errors
- --dl-deps-default
- Override default behaviour for all dependency classes
- pre
- As pre dependencies
- pre-or-post
- As pre dependencies, or post dependencies where needed
- post
- As post dependencies
- try-post
- As post dependencies, with no error for failures
- discard
- Discard
- --dl-installed-deps-pre
- How to handle pre dependencies for installed packages
- pre
- As pre dependencies
- pre-or-post
- As pre dependencies, or post dependencies where needed
- post
- As post dependencies
- try-post
- As post dependencies, with no error for failures
- discard
- Discard (default)
- --dl-installed-deps-runtime
- How to handle runtime dependencies for installed packages
- pre
- As pre dependencies
- pre-or-post
- As pre dependencies, or post dependencies where needed
- post
- As post dependencies
- try-post
- As post dependencies, with no error for failures (default)
- discard
- Discard
- --dl-installed-deps-post
- How to handle post dependencies for installed packages
- pre
- As pre dependencies
- pre-or-post
- As pre dependencies, or post dependencies where needed
- post
- As post dependencies
- try-post
- As post dependencies, with no error for failures (default)
- discard
- Discard
- --dl-uninstalled-deps-pre
- How to handle pre dependencies for uninstalled packages
- pre
- As pre dependencies (default)
- pre-or-post
- As pre dependencies, or post dependencies where needed
- post
- As post dependencies
- try-post
- As post dependencies, with no error for failures
- discard
- Discard
- --dl-uninstalled-deps-runtime
- How to handle runtime dependencies for uninstalled packages
- pre
- As pre dependencies
- pre-or-post
- As pre dependencies, or post dependencies where needed (default)
- post
- As post dependencies
- try-post
- As post dependencies, with no error for failures
- discard
- Discard
- --dl-uninstalled-deps-post
- How to handle post dependencies for uninstalled packages
- pre
- As pre dependencies
- pre-or-post
- As pre dependencies, or post dependencies where needed
- post
- As post dependencies (default)
- try-post
- As post dependencies, with no error for failures
- discard
- Discard
- --dl-uninstalled-deps-suggested
- How to handle suggested dependencies for uninstalled packages (only with --dl-suggested install)
- pre
- As pre dependencies
- pre-or-post
- As pre dependencies, or post dependencies where needed
- post
- As post dependencies (default)
- try-post
- As post dependencies, with no error for failures
- discard
- Discard
- --dl-suggested
- How to handle suggested dependencies
- show
- Display, but do not install (default)
- install
- Install
- discard
- Discard
- --dl-circular
- How to handle circular dependencies
- error
- Raise an error (default)
- discard
- Discard
- --dl-blocks
- How to handle blocks
- accumulate
- Accumulate and show in the dependency list (default)
- error
- Error straight away
- discard
- Discard (dangerous)
- --dl-override-masks
- Zero or more mask kinds that can be overridden as necessary (default: tilde-keyword and license)
- none
- None (overrides defaults, not user selections)
- tilde-keyword
- Keyword masks where accepting ~ would work
- unkeyworded
- Keyword masks where a package is unkeyworded
- repository
- Repository masks
- license
- License masks
- --dl-fall-back
- When to fall back to installed packages
- as-needed-except-targets
- Where necessary, but not for target packages (default)
- as-needed
- Where necessary, including for target packages
- never
- Never
Environment
- IMPORTARE_OPTIONS
- Default command-line options.
Notes
- importare requires a repository with format 'installed_unpackaged' configured and available. It cannot use a standard VDB or suchlike because there is no ebuild available.
- Packages installed using importare will not be visible to broken ebuilds that illegally access the VDB. This means that things like 'built_with_use' will not realise that the package is installed.
Examples
importare --location img/ unpackaged/myapp 1.23
Install the contents of img/ (which could be produced, for example, using 'sudo make DESTDIR=img/ install' from an autotools package) as 'unpackaged/myapp' version 1.23. If 'unpackaged/myapp' is already installed, it will be replaced.
importare --location img/ unpackaged/myapp 1.23 --run-dependency dev-libs/mpfr --run-dependency dev-libs/gmp
As above, and add dependencies. Dependencies are used for resolution and to provide correct output for paludis --uninstall(-unused).
importare --location img/ unpackaged/myapp 1.23 --preserve-metadata
If an existing version of unpackaged/myapp was installed using importare, copies metadata (build and run dependencies, and description) from that version.
importare --location /var/empty sys-apps/portage 2.2
Install an empty fake package named 'sys-apps/portage', version 2.2. DANGEROUS!