From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: "André A. Gomes" <andremegafone@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Guix, ispell.el and FHS
Date: Fri, 24 Sep 2021 11:51:38 +0000 [thread overview]
Message-ID: <toLmEl062kjAciEaffStMF4btdp6aIy1Io3xxsRaA2r8tCSkfBaWVnWdf9uodM1lx8imR5ytZntOyk_jg9gbEF2nfjAqnsZKzU9iRObTOFM=@elenq.tech> (raw)
In-Reply-To: <871r5el490.fsf@gmail.com>
Hi Andre
> I'm relatively new to the GNU/Linux world, so I apologise for any silliness.
>
> I was looking ispell.el and saw:
>
> --8<---------------cut here---------------start------------->8---
> (defcustom ispell-look-command
> (cond ((file-exists-p "/bin/look") "/bin/look")
> ((file-exists-p "/usr/local/bin/look") "/usr/local/bin/look")
> ((file-exists-p "/usr/bin/look") "/usr/bin/look")
> (t "look"))
> "Name of the look command for search processes.
> This must be an absolute file name."
> :type 'file
> :group 'ispell)
> --8<---------------cut here---------------end--------------->8---
>
> That's the usual path for most GNU/Linus distro (FHS compliant). But
> for Guix System users it lives at /run/current-system/profile/bin/look.
>
> It's obvious I can set the variable properly myself.
>
> My question is: what should be done in such cases? I can think of the
> following:
>
> - Patch the Guix package
> - Patch the program itself
> - Nothing (apart from setting things myself)
>
> Thank you.
I'm not a Guix maintainer or anything so get this with a pinch of salt.
First the program itself should be able to find this stuff in a more general
way, not just checking some specific folders.
Second, if the program does not add that change we can patch the guix package
too.
Cheers,
Ekaitz
next prev parent reply other threads:[~2021-09-24 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 9:19 Guix, ispell.el and FHS André A. Gomes
2021-09-24 11:51 ` Ekaitz Zarraga [this message]
2021-09-24 12:38 ` Liliana Marie Prikler
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='toLmEl062kjAciEaffStMF4btdp6aIy1Io3xxsRaA2r8tCSkfBaWVnWdf9uodM1lx8imR5ytZntOyk_jg9gbEF2nfjAqnsZKzU9iRObTOFM=@elenq.tech' \
--to=ekaitz@elenq.tech \
--cc=andremegafone@gmail.com \
--cc=guix-devel@gnu.org \
/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).