From: zimoun <zimon.toutoune@gmail.com>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>, 52259@debbugs.gnu.org
Subject: [bug#52259] [PATCH 3/3] gnu: trytond: Ensure all modules are found.
Date: Tue, 14 Dec 2021 09:15:51 +0100 [thread overview]
Message-ID: <86mtl338lk.fsf@gmail.com> (raw)
In-Reply-To: <0d461f73e5c687d1c53df55540d3248b38349414.1638538371.git.h.goebel@crazy-compilers.com>
Hi,
On Fri, 03 Dec 2021 at 14:41, Hartmut Goebel <h.goebel@crazy-compilers.com> wrote:
> If the python package matching tryton is not installed alongside to trytond,
> PYTHONPATH ist not set (or pointing to a wring version) and trytond (and the
^
typo
> trytond tools) would not find the trytond modules.
>
> This change introduces a new native-search-path GUIX_TRYTOND_MODULES_PATH.
> Trytond gets patched to honor this environment variable.
>
> Thanks to Maxim Cournoyer, who's code for guix-pythonpath-search-path
> was the template for guix-trytonpath-search-path.
The wording appears to me weird, but I am not native.
> * gnu/packages/patches/trytond-add-guix_trytond_path.patch: New file.
Without being picky, why underscore? ^ ^ Otherwise,
gnu/packages/patches/trytond-add_extend_python_path.patch
Well, it does not matter.
Cheers,
simon
next prev parent reply other threads:[~2021-12-14 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 13:39 [bug#52259] [PATCH 1/3] gnu: python-stdnum: Update to 1.17 Hartmut Goebel
2021-12-03 13:41 ` [bug#52259] [PATCH 2/3] gnu: trytond: Fix import of trytond modules Hartmut Goebel
2021-12-03 13:41 ` [bug#52259] [PATCH 3/3] gnu: trytond: Ensure all modules are found Hartmut Goebel
2021-12-14 8:15 ` zimoun [this message]
2021-12-18 14:21 ` Hartmut Goebel
2021-12-18 15:17 ` zimoun
[not found] ` <handler.52259.B.16385387683881.ack@debbugs.gnu.org>
2021-12-18 14:21 ` bug#52259: Acknowledgement ([PATCH 1/3] gnu: python-stdnum: Update to 1.17.) Hartmut Goebel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86mtl338lk.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=52259@debbugs.gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.