From a31834a794394d89bc593671fe5460a93f817d41 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Wed, 11 Oct 2023 07:12:20 +0200 Subject: Clarify bdep-new --package output directory semantics (GH issues #286) --- bdep/new.cli | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/bdep/new.cli b/bdep/new.cli index 5411934..6462f8c 100644 --- a/bdep/new.cli +++ b/bdep/new.cli @@ -43,7 +43,8 @@ namespace bdep project/package (the \cb{--source} form). All the forms except \cb{--source} first create according to a new \cb{build2} project/package called in the subdirectory of the current - working directory (unless overridden with \c{\b{--output-dir}|\b{-o}}). + working directory (unless overridden with \c{\b{--output-dir}|\b{-o}} + or, in case of \cb{--package}, with \c{\b{--directory}|\b{-d}}). If contains a directory component, then the project/package is created in this directory, as if it was specified with \c{\b{--output-dir}|\b{-o}}. @@ -77,8 +78,9 @@ namespace bdep The \cb{--package} form adds the new package to the \cb{packages.manifest} file creating it if necessary. If no project directory is explicitly specified with \c{\b{--directory}|\b{-d}}, then - the current working directory is assumed. Note that nested packages are - not allowed. For example: + it will be deduced from the current working directory (see + \l{bdep-projects-configs(1)} for details on specifying projects). Note + that nested packages are not allowed. For example: \ $ bdep new -t empty hello -- cgit v1.1