From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: File search
Date: Wed, 02 Feb 2022 11:14:47 -0500 [thread overview]
Message-ID: <8735l1z1mw.fsf@gmail.com> (raw)
In-Reply-To: <87zgnlm5ec.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 24 Jan 2022 18:03:15 +0100")
Hi,
Ricardo Wurmus <rekado@elephly.net> writes:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> skribis:
>>
>>> raingloom <raingloom@riseup.net> writes:
>>>
>>>> One use case that I hope can be addressed is TeXlive packages. Trying
>>>> to figure out which package corresponded to which missing file was a
>>>> nightmare the last I had to use LaTeX.
>>>
>>> The texlive package database is the authoritative source of information.
>>> The file texlive.tlpdb is included in the texlive-bin package, and we’re
>>> using it in the importer. I also added (@ (guix import texlive)
>>> files-differ?), which compares a texlive package’s output directory with
>>> the files that the texlive.tlpdb lists for that package.
>>>
>>> You can also use it to check what package should provide a certain file.
>>> I do this all the time to figure out if our existing packages are
>>> incomplete or if we’re just missing a package.
>>
>> Oh, I had never tried that. Is there a command that browses
>> texlive.tlpdb, or do you just open it or grep it?
>
> I just have it open in Emacs and search inside. But we could easily add
> a procedure to (guix import texlive) to check the texlive.tlpdb. All
> the hard work has already been done; we’re using the same mechanism for
> the importer and “files-differ?”.
It used to be broken, but with the c-u-f merge the 'tlmgr' tool now
works as expected to search for things in the local texlive.tlpdb
database:
--8<---------------cut here---------------start------------->8---
$ guix shell --pure texlive-bin grep which coreutils sed gnupg -- tlmgr info cite.sty
tlmgr: cannot find package cite.sty, searching for other matches:
Packages containing `cite.sty' in their title/description:
Packages containing files matching `cite.sty':
abntex2:
texmf-dist/tex/latex/abntex2/abntex2cite.sty
apacite:
texmf-dist/tex/latex/apacite/apacite.sty
chscite:
texmf-dist/tex/latex/chscite/chscite.sty
cite:
texmf-dist/tex/latex/cite/cite.sty
texmf-dist/tex/latex/cite/drftcite.sty
texmf-dist/tex/latex/cite/overcite.sty
combine:
texmf-dist/tex/latex/combine/combcite.sty
computational-complexity:
texmf-dist/tex/latex/computational-complexity/cc2cite.sty
texmf-dist/tex/latex/computational-complexity/cccite.sty
emojicite:
texmf-dist/tex/lualatex/emojicite/emojicite.sty
gcite:
texmf-dist/tex/latex/gcite/gcite.sty
icite:
texmf-dist/tex/latex/icite/icite.sty
kluwer:
texmf-dist/tex/latex/kluwer/klucite.sty
lwarp:
texmf-dist/tex/latex/lwarp/lwarp-cite.sty
texmf-dist/tex/latex/lwarp/lwarp-drftcite.sty
mcite:
texmf-dist/tex/latex/mcite/mcite.sty
notoccite:
texmf-dist/tex/latex/notoccite/notoccite.sty
velthuis:
texmf-dist/tex/latex/velthuis/dvngcite.sty
xcite:
texmf-dist/tex/latex/xcite/xcite.sty
--8<---------------cut here---------------end--------------->8---
It's not great that references to 'grep which coreutils sed gnupg'
aren't patched though (I thought I cared they were, perhaps it
regressed).
HTH,
Maxim
next prev parent reply other threads:[~2022-02-02 17:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 9:03 File search Ludovic Courtès
2022-01-21 10:35 ` Mathieu Othacehe
2022-01-22 0:35 ` Ludovic Courtès
2022-01-21 19:00 ` Vagrant Cascadian
2022-01-22 0:37 ` Ludovic Courtès
2022-01-22 2:53 ` Maxim Cournoyer
2022-01-25 11:15 ` Ludovic Courtès
2022-01-25 11:20 ` Oliver Propst
2022-01-25 11:22 ` Oliver Propst
2022-01-22 4:46 ` raingloom
2022-01-22 7:55 ` Ricardo Wurmus
2022-01-24 15:48 ` Ludovic Courtès
2022-01-24 17:03 ` Ricardo Wurmus
2022-02-02 16:14 ` Maxim Cournoyer [this message]
2022-02-05 11:15 ` Ludovic Courtès
2022-01-25 23:45 ` Ryan Prior
2022-02-05 11:18 ` Ludovic Courtès
2022-02-06 13:27 ` André A. Gomes
-- strict thread matches above, loose matches on Subject: below --
2022-12-02 17:58 antoine.romain.dumont
2022-12-02 18:22 ` Antoine R. Dumont (@ardumont)
2022-12-03 18:19 ` Ludovic Courtès
2022-12-04 16:35 ` Antoine R. Dumont (@ardumont)
2022-12-06 10:01 ` Ludovic Courtès
2022-12-06 12:59 ` zimoun
2022-12-06 18:27 ` (
2022-12-08 15:41 ` Ludovic Courtès
2022-12-09 10:05 ` Antoine R. Dumont (@ardumont)
2022-12-09 18:05 ` zimoun
2022-12-11 10:22 ` Ludovic Courtès
2022-12-15 17:03 ` Antoine R. Dumont (@ardumont)
2022-12-19 21:25 ` Ludovic Courtès
2022-12-19 22:44 ` zimoun
2022-12-20 11:13 ` Antoine R. Dumont (@ardumont)
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735l1z1mw.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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/guix.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).