Re: global commands

Laurent Bercot <[email protected]> wrote:
> Stefan Karrmann <[email protected]> wrote:
>> How can I find all globally registered commands of package foo?
>>
>> 1. Take all files in /package/foo/command ?

That's my vote.

>  I think using /package/foo/command is a good convention for foo's
> commands, but there is no reason not to include unregistered commands.
> Some of my packages export only part of the commands that are listed
> in /package/foo/command .

I'd rather put unregistered commands in a separate directory.  That
way, we get the list of registered commands for free: command/*.

>> If the globally registered commands are declared in a file like in (2)
>> a slash-package manager can easily use this information to update
>> /command.

The same is true for (1): the file could be a directory.  That's the
natural way to represent a list in the filesystem.


paul