From: Kristofer Buffington <kristoferbuffington@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 29301@debbugs.gnu.org
Subject: [bug#29301] [PATCH] substitute* hard-coded paths with paths from "out"
Date: Tue, 28 Nov 2017 16:10:35 -0500 [thread overview]
Message-ID: <CAN1Dt4SP3_Y8eG2YqBQZbgLsFLRSqtjOjeKCYXpjd_PHCJkx-Q@mail.gmail.com> (raw)
In-Reply-To: <87r2sknlxv.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
Cool! I am not very familiar with autotools. I appreciate the help! I will
follow up with a new patch.
Thanks
Kris
On Nov 27, 2017 3:52 AM, "Ludovic Courtès" <ludo@gnu.org> wrote:
> Hi,
>
> (Please always keep the bug Cc’d.)
>
> Kristofer Buffington <kristoferbuffington@gmail.com> skribis:
>
> > 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?
>
> --sysconfdir would not change the hard-coded file names, but it would
> actually make those hard-coded file names valid. And again, using /etc
> as the sysconfdir would allow people to have a writable artanis.conf
> file, for instance, so that’s definitely something we should do.
>
> Thanks,
> Ludo’.
>
[-- Attachment #2: Type: text/html, Size: 1451 bytes --]
next prev parent reply other threads:[~2017-11-28 21:11 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 ` [bug#29301] Fwd: " Kristofer Buffington
2017-11-27 8:51 ` Ludovic Courtès
2017-11-28 21:10 ` Kristofer Buffington [this message]
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=CAN1Dt4SP3_Y8eG2YqBQZbgLsFLRSqtjOjeKCYXpjd_PHCJkx-Q@mail.gmail.com \
--to=kristoferbuffington@gmail.com \
--cc=29301@debbugs.gnu.org \
--cc=ludo@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).