This one is a little funny — for a long time now packages have used the description and/or summary metadata keys in zkg.meta to describe the package. zkg however only knows description, and when it needs to come up with a one-liner for the package it simply uses the first line of the description.
It looks like I actually further cemented use of summary further when I added it to the templates' zkg.meta. Sigh. Either way, there are lots of packages in the default source that use it.
I'm thinking we shoud simply support summary as the preferred way to give a quick summary when it's available, and fall back to using description's first line as summary when it's not.
This one is a little funny — for a long time now packages have used the
descriptionand/orsummarymetadata keys in zkg.meta to describe the package. zkg however only knowsdescription, and when it needs to come up with a one-liner for the package it simply uses the first line of the description.It looks like I actually further cemented use of
summaryfurther when I added it to the templates' zkg.meta. Sigh. Either way, there are lots of packages in the default source that use it.I'm thinking we shoud simply support
summaryas the preferred way to give a quick summary when it's available, and fall back to usingdescription's first line as summary when it's not.