Bug#881692: command-not-found: I re-wrote command-not-found

Julian Andres Klode jak at debian.org
Fri Nov 17 08:53:41 UTC 2017

On Thu, Nov 16, 2017 at 11:55:07PM -0800, Shawn Landden wrote:
> On Thu, Nov 16, 2017 at 11:39 PM, Xen <list at xenhideout.nl> wrote:
> > Julian Andres Klode schreef op 14-11-2017 8:50:
> >
> > * You should not depend on grep, sed, coreutils, they are Essential.
> >>
> >
> > Can I ask what this means?
> >
> > I actually assume that these dependencies are not *required*, not that you
> > can't use the tools.
> Required: yes. The highest priority. sysvinit was Required: yes until
> systemd came along https://www.debian.org/doc/debian-policy/#priorities

What it actually means is that you don't have to declare them in Depends
fields. And required is a priority, that's distinct. Essential basically
is the set of packages dpkg needs for its own operation.

> Speaking of, I can't use 'apt-get indextargets' from shell and had to
> rewrite in ruby, because sed doesn't not support lazy matching, and I don't
> know how else to match NOT \n\n. (it also doesn't seem to support multiples
> of submatches.) Old regular expression implementations are showing their
> age (not to mention perl's non-regular features).

Ruby is just a major no go. At that system level, the best choices
are Perl, Shell, and C++. Maybe Python (on Ubuntu it's in ubuntu-minimal,
but in Debian it's only used by standard priority and less, perl on the
other hand is required and essential). Ruby has the lowest priority
- optional.

Debian Developer - deb.li/jak | jak-linux.org - free software dev
Ubuntu Core Developer                              de, en speaker

More information about the Ubuntu-devel-discuss mailing list