dylan new dependency

[cgay]

For later... It might be worth having a dylan new [dev] dependency pkg1 [pkg2 ...] subcommand since it could

• verify that the dep exists
• verify that the dep doesn't conflict
• prevent simple syntax errors in the package file

[housel]

Most things I've seen that have this don't need a separate dependency keyword, they just treat every positional arg after the first one as a dependency.

[cgay]

Are you arguing against the use of multi-level subcommands like new library, new application, and new dependency?

The [dev] in the original description might've been confusing, but the idea was to add two new subcommands to the new subcommand:

1. dylan new dependency
2. dylan new dev dependency

This whole multi-level subcommand idea would be a lot nicer with LispM-like completion facilities, or at a minimum, with the ability to abbreviate to anything that uniquely names a full command, like dylan new d d or dylan new app.