From: Kristofer Buffington <kristoferbuffington@gmail.com>
To: 29301@debbugs.gnu.org
Subject: [bug#29301] Fwd: [bug#29301] [PATCH] substitute* hard-coded paths with paths from "out"
Date: Sun, 26 Nov 2017 20:31:52 -0500 [thread overview]
Message-ID: <CAN1Dt4RVo6dVwHDFZDiVgX3Ce-Wx=_xVqv2vjPuazF10_+PYRQ@mail.gmail.com> (raw)
In-Reply-To: <CAN1Dt4RZ3Mv5HBarSCPqoVRrXqa7bojZ-SRyEOrr2CqaaTu8cA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1629 bytes --]
---------- Forwarded message ----------
From: Kristofer Buffington <kristoferbuffington@gmail.com>
Date: Sun, Nov 26, 2017 at 8:30 PM
Subject: Re: [bug#29301] [PATCH] substitute* hard-coded paths with paths
from "out"
To: Ludovic Courtès <ludo@gnu.org>
I will investigate. There are some hard coded paths in artanis/config.scm
looking for the configuration file in /etc/artanis/artanis.conf -- I don't
believe the --sysconfdir flag will have any impact on the hard-coded paths.
Perhaps I should send a patch upstream to eliminate the hard paths? Then
the substitute* would be unnecessary?
Thanks!
Kris
On Thu, Nov 23, 2017 at 4:59 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> Hi Kristofer,
>
> Kristofer Buffington <kristoferbuffington@gmail.com> skribis:
>
> > * gnu/packages/guile.scm
> > used substitute* to correct some hardcoded paths in the artanis package
>
> [...]
>
> > + (substitute* "artanis/config.scm"
> > + (("/etc/artanis/artanis.conf")
> > + (string-append out "/etc/artanis.conf"))
> > + (("/etc/artanis/pages")
> > + (string-append out "/etc/artanis")))
> > + (substitute* "etc/artanis/artanis.conf"
> > + (("/etc/artanis/pages")
> > + (string-append out "/etc/artanis")))
>
> Shouldn’t we instead configure it with --sysconfdir=/etc? That would
> allow users to provide custom configuration files, whereas currently
> OUTPUT/etc/artanis contains immutable configuration files.
>
> WDYT?
>
> Thanks,
> Ludo’.
>
[-- Attachment #2: Type: text/html, Size: 2594 bytes --]
next prev parent reply other threads:[~2017-11-27 1:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 0:41 [bug#29301] [PATCH] substitute* hard-coded paths with paths from "out" Kristofer Buffington
2017-11-23 21:59 ` Ludovic Courtès
[not found] ` <CAN1Dt4RZ3Mv5HBarSCPqoVRrXqa7bojZ-SRyEOrr2CqaaTu8cA@mail.gmail.com>
2017-11-27 1:31 ` Kristofer Buffington [this message]
2017-11-27 8:51 ` Ludovic Courtès
2017-11-28 21:10 ` Kristofer Buffington
2018-02-06 15:13 ` Ludovic Courtès
[not found] ` <CAN1Dt4QCrNX3HT6w-zn5AkXTKMJ_WZYxmmHgfzKVBb4jkhSUcQ@mail.gmail.com>
2018-02-09 14:15 ` Kristofer Buffington
2022-01-13 15:56 ` zimoun
2022-01-17 13:18 ` bug#29301: " Ludovic Courtès
2019-09-27 13:07 ` [bug#29301] " Tobias Geerinckx-Rice via Guix-patches via
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='CAN1Dt4RVo6dVwHDFZDiVgX3Ce-Wx=_xVqv2vjPuazF10_+PYRQ@mail.gmail.com' \
--to=kristoferbuffington@gmail.com \
--cc=29301@debbugs.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).