RE: Adding a few more finder keywords

[Drew Adams]

>  > We could decide that the specific keywords are unwanted, tho.
> 
> An "unwanted" keyword doesn't exist though.  Somebody wanted it or
> it wasn't in Keywords: in the first place.  And although every human
> is unique, very few humans are so unique that they'll choose a keyword
> that nobody else would use to look up packages.
> 
> So I think what you mean by "unwanted" is mostly "redundant (because
> a> synonym)". It seems to me that
> 
> 1.  There *should* be a list of "recommended keywords" which package
>     maintainers can easily access for reference...
> 2.  There *should* be a database of synonyms of recommended keywords
>     for use by maintainers...
> 3.  There should be a tool to walk the libraries...
>     Probably this tool only needs to be run at release time...
> 
>     There's no need to be fascist about keyword maintenance...

I pretty much agree with all of those points, as being good things
to have.  But possibilities that work only with a set of
"recommended", predefined keywords, e.g. for the package system,
should use a different file-header keyword from `Keywords:'.  You
want something different from what `Keywords:' has always been,
something that conflicts with its usage?  Fine, just add a new
file-header keyword for that.  Happiness all around.

However, just as we should not co-opt `Keywords:', so we should
not co-opt `finder'.  Finder works with `Keywords:' in a particular
way. It is fine to extend finder so that it does additional things,
for particular use cases or in particular environments (e.g., for
Emacs maintainers or for the package system), but what it does
with `Keywords:' should not be cannibalized for the new features.

Again, let it do those things with a new file-header keyword.
If some of the things finder will do are the same, then let it
do them with both `Keywords:' and the new file-header keyword.
IOW, to the extent that some part of the updated finder does not
conflict with the normal interpretation/use of `Keywords:', let
it be used for both.

Should be a no-brainer.  `Keywords:' ain't broke; don't "fix" it.
Feel free to add new features that do something different and
have a different motivation.  But don't bother `Keywords:' just
to implement what you need.  It's not hard for you to leave
`Keywords:' alone, for its original, more flexible, use cases.