I depend upon command-not-found to keep me sane. It has helped me fifty or more times over the last few years.<br><br><div class="gmail_quote">On 18 August 2010 18:19, Stefan Potyra <span dir="ltr"><<a href="mailto:stefan.potyra@informatik.uni-erlangen.de">stefan.potyra@informatik.uni-erlangen.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi,<br>
<br>
Am Wednesday 18 August 2010 23:53:45 schrieb Dustin Kirkland:<br>
<div class="im">> On Aug 18, 2010 at 1:42 PM, Barry Warsaw <<a href="mailto:barry@canonical.com">barry@canonical.com</a>> wrote:<br>
> > On Aug 18, 2010, at 01:12 PM, Mathias Gug wrote:<br>
> >>IMO the command-not-found package is very useful for server<br>
> >>installation. So I'd like to keep it when a system is installed from<br>
> >>the -server iso.<br>
> ><br>
> > I hope it will be kept for desktop as well. I think it's a very useful<br>
> > tool.<br>
><br>
> +1 for command-not-found on both Desktop and Server. It's one of the<br>
> most useful, unique, and friendly tools in Ubuntu, IMO.<br>
<br>
</div>*'shameless plug*: command-not-found doesn't appear to be in a well-maintained<br>
state in Ubuntu, otherwise this bug would have been not around for maverick:<br>
<br>
<<a href="https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/538306" target="_blank">https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/538306</a>><br>
<br>
So at the moment, I consider command-not-found as not ready for a default<br>
installation on either image, and would be very happy to be proved wrong :).<br>
<br>
Cheers,<br>
<font color="#888888"> Stefan.<br>
</font><br>--<br>
ubuntu-devel mailing list<br>
<a href="mailto:ubuntu-devel@lists.ubuntu.com">ubuntu-devel@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel</a><br>
<br></blockquote></div><br>Yours,
<div>Anzan</div>