dubx ~main

= dubx

Thin meta-CLI for D package workflows. It does not reimplement the backends — it routes to them:

• Build / resolve → https://code.dlang.org/packages/redub[redub] (falls back to dub if redub is missing)
• Registry owner ops → https://github.com/dlang-supplemental/dub-publish[dub-publish] (register, login, hooks, logo, …)

Official dub has no publish command; redub is a separate build system. dubx is the small glue so you do not have to remember which binary owns which verb.

== Install

[source,console]

git clone https://github.com/dlang-supplemental/dubx.git cd dubx dub build --build=release

Put dubx on your PATH, plus the backends you use:

[source,console]

build backend (recommended)

dub fetch redub

put the redub binary on PATH, or: dub run redub -- build

registry backend

git clone https://github.com/dlang-supplemental/dub-publish.git cd dub-publish && dub build --build=release

Check discovery:

[source,console]

dubx which

== Usage

[source,console]

dubx build dubx test dubx run -- --help

dubx login --user you --save-credentials dubx publish --ignore-fork dubx hooks -n mypkg dubx update -n mypkg

Passthrough escapes:

[source,console]

dubx redub build --compiler=ldc2 dubx dub build dubx dub-publish status -n mypkg

== Design

• No forking of redub or dub — stay out of build-system compatibility debt.
• Registry features stay in dub-publish.
• dubx only maps verbs → executables on PATH (and siblings next to the dubx binary).

== Changelog

See link:CHANGELOG.adoc[CHANGELOG].

== License

Boost Software License 1.0.