---
name: "dpt-config"
section: "5"
platform: "linux"
package: "pkg-perl-tools"
version: "0.82"
release: "Debian 13 (Trixie)"
platforms: ["linux"]
url: "https://new.carta.tech/dpt-config"
---

# dpt-config(5)

dpt configuration

## NAME

dpt-config - dpt configuration

## DESCRIPTION

[**dpt**(1)](/dpt/1.md) configuration lives in plain text files using POSIX shell syntax. The files are sourced by the tools, not parsed.

## LOCATION

Configuration files are looked for in the following locations, in order, and every found file is sourced by the script, later files possibly overriding the previous ones.

- *~/.dpt.conf*

  - *~/.config/dpt.conf*

  ## TIPS & TRICKS

### Run dpt(1) from git

When bugs in [**dpt**(1)](/dpt/1.md) are fixed or new features are implemented in git but not yet available in the uploaded version, you may want to run dpt and its sub-scripts from your local clone of the **pkg-perl-tools** repository. This can be done by setting the following variables in *.dpt.conf*:

```
    # needed anyway, adjust path
    DPT_PACKAGES=~/src/pkg-perl/packages
    # specific for running from git
    DPT__SCRIPTS=$DPT_PACKAGES/pkg-perl-tools/scripts
    export PERL5LIB=$DPT_PACKAGES/pkg-perl-tools/lib
```

### Storing tokens

If you keep your configuration files in a (potentially) public git repository, you might be wary of sticking tokens like *DPT\_GITHUB\_OAUTH* or *DPT\_SALSA\_PRIVATE\_TOKEN* in your *.dpt.conf*. As *.dpt.conf* is just a shell fragment which gets sourced, you can put those variables in a different file (and don't commit this one). E.g.

```
    [ ! -e ~/.dpt.conf.$(hostname) ] || . ~/.dpt.conf.$(hostname)
```

## COPYRIGHT & LICENSE

Copyright 2013 Damyan Ivanov dmn@debian.org

Copyright 2018-2021 gregor herrmann gregoa@debian.org

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.