Ticket #439 (new enhancement)

Opened 12 years ago

Last modified 11 years ago

Generate command-not-found database for Debathena

Reported by: broder Owned by:
Priority: low Milestone: The Distant Future
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:

Description

Even if we can't directly use command-not-found as a whichlocker substitute, we should still build a command-not-found database for Debathena packages and ship it as part of debathena-standard.

Otherwise, you end up with this:

evan@tracey:~$ stella
The program 'stella' is currently not installed.  You can install it by typing:
sudo apt-get install stella
stella: command not found

Change History

comment:1 Changed 12 years ago by andersk

In this case, given that stella is already a required dependency of debathena-standard, it doesn’t help to also include with debathena-standard a database that tells you where to get stella.

Do you think there’s a case in which it does help?

comment:2 Changed 11 years ago by broder

Hmm...I guess stella is a bad example here. But there still is at least a little bit of software that we only ship in login-graphical+

Looking at our Contents file, I see things like our acroread wrapper, update_test, xmoira. Maybe that's it.

In any case, if we do decide we want to do this, it looks fairly easy - I think we just drop gdbm .db files in /usr/share/command-not-found/programs.d. command-not-found appears to generate those database files by querying apt - we could probably cargo-cult its code to implement this.

Note: See TracTickets for help on using tickets.