unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Prafulla Giri <pratheblackdiamond@gmail.com>
To: 44309@debbugs.gnu.org
Subject: [bug#44309] Further Cleanups
Date: Sun, 1 Nov 2020 10:29:36 +0545	[thread overview]
Message-ID: <CAFw+=j1SZSf6F-bp2wqFe3oWrZBN-=82zArWRYEs1qf86HpA+g@mail.gmail.com> (raw)
In-Reply-To: <CAFw+=j2NSyb3YywVU1t4JtPF-Y9JBoLjW-m5cqHQ9VEpuO+i0w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

 I am wondering if the python bindings should be separated into an output.
gnucash:python perhaps. That is the route that the Ubuntu developers seem
to have taken. `apt show python3-gnucash`. It would actually make even more
sense with guix as one could use flatpak-installed gnucash for their daily
usage, and then from their /usr/bin/python3 or $GUIX_PROFILE/bin/python3
they could use gnucash programmatically via the bindings.

However, I am not sure if it is possible to specify a
search-path-specification for a particular output of a package. I don't
know much about splitting packages into outputs either. If we had
gnucash:python, and a user ran `guix install gnucash:python`, would that
only get the user /gnu/store/...-gnucash-x.y-python from the substitute
server and save them bandwidth?

If anybody is willing to give me some pointers as to how I could go about
cleanly splitting gnucash into gnucash:python - with the
native-search-path-specification for PYTHONPATH only being declared for
gnucash:python (and that will be an absolute must), I am more than happy to
clean this patch up.

Thank you.

[-- Attachment #2: Type: text/html, Size: 1228 bytes --]

  reply	other threads:[~2020-11-01  4:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 15:29 [bug#44309] [PATCH] gnu: gnucash: Enable python bindings Prafulla Giri
2020-11-01  4:44 ` Prafulla Giri [this message]
2020-11-02 13:52 ` [bug#44309] New and Improved Patch Prafulla Giri
2020-11-10 21:10   ` bug#44309: " Marius Bakke
2020-11-11  9:26     ` [bug#44309] " Prafulla Giri

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='CAFw+=j1SZSf6F-bp2wqFe3oWrZBN-=82zArWRYEs1qf86HpA+g@mail.gmail.com' \
    --to=pratheblackdiamond@gmail.com \
    --cc=44309@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).