On Wednesday, 13 April 2016 at 16:34:16 UTC, Jon D wrote:

> Thanks Rory, Puming. I'll look into this and see how best to make it fit. I'm realizing also there's one additional capability it'd be nice to have in dub for tools like this, which in an option to install the executables somewhere that can be easily be put on the path. Still, even without this there'd be benefit to having them fetched via dub.
>
> --Jon

Well, you can do that:

In the subpackage dub.sdl, add targetPath:



 ```
 name "app1"
 targetType "executable"
 targetPath "../bin/"
 dependency "myapp:common" version="*"
 ```

On Wednesday, 13 April 2016 at 17:21:58 UTC, Jon D wrote:
> On Wednesday, 13 April 2016 at 17:01:33 UTC, Dicebot wrote:
>> On Wednesday, 13 April 2016 at 16:34:16 UTC, Jon D wrote:
>>> [...]
>>
>> You don't need to put anything on path to run utils from dub packages. `dub run` will take care of setting necessary envionment (without messing with the system):
>>
>> dub fetch package_with_apps
>> dub run package_with_apps:app1 --flags args
>
> These are command line utilities, along the lines of unix 'cut', 'grep', etc, intended to be used as part of unix pipeline. It'd be less convenient to be invoking them via dub. They really should be on the path themselves.
>
> --Jon

if dub supports something like:

```
dub deploy
```

and you can specifiy some dir like '/usr/bin/' in the dub.sdl,

it would be great

On Wednesday, 13 April 2016 at 16:34:16 UTC, Jon D wrote:
> On Wednesday, 13 April 2016 at 07:34:11 UTC, Rory McGuire wrote:
>> On Wed, Apr 13, 2016 at 3:41 AM, Puming via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote:
>>
>>>> On Tuesday, 12 April 2016 at 06:22:55 UTC, Puming wrote:
>>> Here is what I know of it, using subPackages:
>>
>> Just tried your suggestion and it works. I just added the below to the
>> parent project to get the apps build:
>> void main() {
>> import std.process : executeShell;
>> executeShell(`dub build :app1`);
>> executeShell(`dub build :app2`);
>> executeShell(`dub build :app3`);
>> }
>
> Thanks Rory, Puming. I'll look into this ...
>
Available now via DUB. Setup follows the outline Rory and Puming suggested, plus a few other changes. Only useful for people already using DUB, but seems convenient and does get it included in the package registry. Works as follows:
   $ dub fetch tsv-utils-dlang
   $ dub run tsv-utils-dlang
This kicks off a build of the package, binaries are in the DUB package repository. The user has to add them to the PATH.