Searching for “LocalAI” doesn’t return the LocalAI package

When searching for “LocalAI” on NixOS Search, the package is missing from the search results, apparently because it’s named after the local-ai executable instead of the project.

What can be done to make the package show up when searching for the project name?

Also the pname and the local-ai executable choice is a bit superficial, see:

Does upstream’s docs mention the local-ai executable? If not, it’d be worth talking about this issue with the maintainers of this package, via a GitHub issue (ccing them of course).

Yep:

Include it in meta.description or meta.longDescription, based on the search result for aichat which does so.

Do you think that would conflict with the intent of this convention?

meta.description […] should not refer to the package name

I mean, the originating message is that the local-ai package isn’t named LocalAI. :slightly_smiling_face:

The current meta.description is OpenAI alternative to run local LLMs, image and audio generation, which likely comes from previous marketing copy on the LocalAI website.

Today, that marketing copy is “LocalAI is the free, Open Source OpenAI alternative”. (Bold in the original.)

I’m not a stickler for these sorts of rules, and I wouldn’t mind that as the description. But sticklers abound and I don’t feel strongly enough on the matter to fight with them.

Ideally there’d be a meta.keywords or something equivalent, and naturally, I’m not the first to think of this (though the linked issue is about NixOS options):

Or perhaps even setting meta.longDescription would work (if it’s used in searches?)

1 Like