From: David Bremner <david@tethera.net>
To: Ralph Seichter <ralph@ml.seichter.de>, notmuch@notmuchmail.org
Subject: Re: Dependencies should include "realpath"
Date: Sat, 17 Oct 2020 08:18:33 -0300 [thread overview]
Message-ID: <87pn5hw16e.fsf@tethera.net> (raw)
In-Reply-To: <87o8l1r6u0.fsf@wedjat.horus-it.com>
Ralph Seichter <ralph@ml.seichter.de> writes:
> * David Bremner:
>
>> Do you have a suggested replacement? I guess some inline perl with "use
>> Cwd 'realpath'" would probably work, although I haven't tested it.
>
> At a quick glance, that particular section of "configure" is run by
> doc/conf.py to generate three lines of Python code and store the result
> as sphinx.config, correct? If so, my preferred choice would be to use
> Python to figure out the absolute path, e.g. like so:
>
> rsti_dir = os.path.abspath('emacs')
>
> This shows the generated result, and I assume that emacs is a directory
> in the source tree? I also wonder if an absolute directory path is really
> required for the doc-build to work.
Someone (TM) would have to check that this version did not break
out-of-tree builds. Other than that it seems plausible.
> The segment of conf.py which uses the generated config file does not
> look convincing to me anyway. Apparently the original author did not
> like it either, which is why the segment is labelled as "hacky". It
> should probably be overhauled, and not only because it uses the
> statement open(rsti_dir+'/'+file) which will potentially fail, depending
> on the build platform.
It's somewhat orthogonal to this discussion, but I don't object to a
patch replacing the hardcoded '/' with the appropriate python path
manipulation code. I think windows compatibility for notmuch has much
bigger issues, but it doesn't hurt to clean up the code.
Other than that, I'm not sure what an "overhaul" would involve.
d
next prev parent reply other threads:[~2020-10-17 11:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 20:42 Dependencies should include "realpath" Ralph Seichter
2020-10-17 0:18 ` David Bremner
2020-10-17 1:15 ` Ralph Seichter
2020-10-17 11:18 ` David Bremner [this message]
2020-10-17 23:08 ` Ralph Seichter
2020-10-19 18:48 ` Tomi Ollila
2020-10-20 14:54 ` Ralph Seichter
2020-10-20 15:06 ` Tomi Ollila
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pn5hw16e.fsf@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=ralph@ml.seichter.de \
/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://yhetil.org/notmuch.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).