From: Nick Dokos <nicholas.dokos@hp.com>
To: Olaf Meeuwissen <olaf.meeuwissen@avasys.jp>
Cc: Jude DaShiell <jdashiel@shellworld.net>,
nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: why was makefile changed to produce this?
Date: Tue, 18 Oct 2011 19:41:16 -0400 [thread overview]
Message-ID: <16904.1318981276@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from Olaf Meeuwissen <olaf.meeuwissen@avasys.jp> of "Wed, 19 Oct 2011 08:14:54 +0900." <87r529ao41.fsf@avasys.jp>
Olaf Meeuwissen <olaf.meeuwissen@avasys.jp> wrote:
> > Here is a useful command that you can use on Debian and Ubuntu systems
> > in situations like this:
> >
> > $ dpkg -S makeinfo
> > texinfo: /usr/bin/makeinfo
> > octave3.2-common: /usr/share/octave/3.2.4/m/help/__makeinfo__.m
> > emacs23-common: /usr/share/emacs/23.1/lisp/textmodes/makeinfo.elc
> > texinfo: /usr/share/man/man1/makeinfo.1.gz
>
> This only works for installed packages, though, as it searches the files
> below /var/lib/dpkg/info, IIRC.
> BTW, dpkg forwards that request to dpkg-query.
>
Ah, you are right: it's only useful after the fact.
Nick
> > [...]
> >
> > $ goo
> > The program 'goo' is currently not installed. To run 'goo' please ask your administrator to install the package 'goo'
>
> In which case `apt-cache show goo` may be of help.
>
> Hope this helps,
> --
> Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION
> FSF Associate Member #1962 Help support software freedom
> http://www.fsf.org/jf?referrer=1962
>
next prev parent reply other threads:[~2011-10-18 23:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 8:27 why was makefile changed to produce this? Jude DaShiell
2011-10-18 12:49 ` Nick Dokos
2011-10-18 23:14 ` Olaf Meeuwissen
2011-10-18 23:41 ` Nick Dokos [this message]
2011-10-19 11:26 ` Rémi Vanicat
2011-10-19 14:59 ` Nick Dokos
-- strict thread matches above, loose matches on Subject: below --
2011-10-18 5:02 Jude DaShiell
2011-10-18 7:15 ` Michael Brand
2011-10-18 7:54 ` Jude DaShiell
2011-10-18 8:41 ` Olaf Meeuwissen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16904.1318981276@alphaville.americas.hpqcorp.net \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=jdashiel@shellworld.net \
--cc=olaf.meeuwissen@avasys.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).