From: Raghav Gururajan via Guix-patches via <guix-patches@gnu.org>
To: phodina <phodina@protonmail.com>
Cc: 60316@debbugs.gnu.org, Marius Bakke <marius@gnu.org>
Subject: [bug#60316] [PATCH] WIP: Add homeassistant.
Date: Mon, 26 Dec 2022 00:11:49 -0500 [thread overview]
Message-ID: <634278b7-4dd9-a561-e022-0cde3b6714d9@raghavgururajan.name> (raw)
In-Reply-To: <znLeCLDDKDEAuidADwa4L37YXCFmY8MRGVnIFwtk9zLJm8-Rlp-W7sJE51_TX9pKULrR81C6oOa6LCZ0LphgU27otG_eU696FPXlPwobo5I=@protonmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 790 bytes --]
Petr,
> I'd love to add Home assistant to Guix to liberate our homes :-D
Woah! Thanks so much for working on this. I've been eyeing at
homeassitant for a while. :D
> However, it has one nasty problem. There's one Python module 'orjson' which depends on rust package [1]. Since it would mean to add a lot of Rust packages I'd like to ask for help if there isn't a better way to build the package 'orjson'?
I'd like to help. Let's see if we can avoid that dependency. If we
can't, I'll aid this work with packing the related rust packages.
> Just out of curiosity have you been able to package the Home assistant?
Darn! I forgot that I created that post. I must've working on that and
lost the work because of SSD failure happened midst 2021. :(
Regards,
RG.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-12-26 5:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-25 17:24 [bug#60316] [PATCH] WIP: Add homeassistant phodina via Guix-patches via
2022-12-26 5:11 ` Raghav Gururajan via Guix-patches via [this message]
2022-12-27 22:06 ` phodina via Guix-patches via
2023-01-14 19:54 ` phodina via Guix-patches via
2023-01-16 3:53 ` Raghav Gururajan 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=634278b7-4dd9-a561-e022-0cde3b6714d9@raghavgururajan.name \
--to=guix-patches@gnu.org \
--cc=60316@debbugs.gnu.org \
--cc=marius@gnu.org \
--cc=phodina@protonmail.com \
--cc=rg@raghavgururajan.name \
/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).