You can use `bin/bin-env-util` to create and query binary environments.
You can use `poulpe bin-env-util` to create and query binary environments.
The `setup-one` command will run a script that takes care of setting up the environment. There is currently only one script in this repository (which sets up a Mercurial repository), feel free to adapt and create your own.
Example:
```console
...
...
@@ -26,9 +26,9 @@
The `setup-one` command will run a script that takes care of setting up the environment. There is currently only one script in this repository (which sets up a Mercurial repository), feel free to adapt and create your own.
You can make sure the environment is setup correctly:
```console
$./bin/env-desc show $DATA_DIR/bin-envs/mercurial-6.4rc0-rhg/bin-env.poulpe
$poulpe env-desc show $DATA_DIR/bin-envs/mercurial-6.4rc0-rhg/bin-env.poulpe
bin-env-vars:
hg:
changeset:
...
...
@@ -60,7 +60,7 @@
You can query the environment for information:
```console
$./bin/env-desc get $DATA_DIR/bin-envs/mercurial-6.4rc0-rhg/bin-env.poulpe bin-env-vars.hg.changeset.node
$poulpe env-desc get $DATA_DIR/bin-envs/mercurial-6.4rc0-rhg/bin-env.poulpe bin-env-vars.hg.changeset.node
05de4896508e8ec387b33eb30d8aab78d1c8e9e4
```
...
...
@@ -73,8 +73,6 @@
Creating a data-env
===================
XXX You need to add `/path/to/poulpe/bin` to your `$PATH`. This will be fixed shortly.
There are a few scripts to help setting up a data environment in `suites/hg/setup-data`.
They are all specific to setting up an existing Mercurial clone, feel free to create your own.
...
...
@@ -99,8 +97,8 @@
Running a benchmark
===================
You can use `bin/run-util` to run a benchmark. There are many benchmarks in `suites/hg/benchmarks` that are specific to benchmarking Mercurial. Feel free to create your own.
You can use `poulpe run-util` to run a benchmark. There are many benchmarks in `suites/hg/benchmarks` that are specific to benchmarking Mercurial. Feel free to create your own.