Re: Packaging a python package that is using setuptools_rust

[phodina]

Hi Hamzeh and Lars,

> Hi Hamzeh,
>
> > I want to package the `etebase-py` library: 
> > https://github.com/etesync/etebase-py/
>
> did you manage to package this library? I’m also interested in it,
>
> because I want to try etesync-dav.
>
> Thanks,
>
> Lars

I'm also interested in packaging this Python module as Rust makes it's way into 
Python universe.

Also since it's setuptools should we also modify the Python build system?


Petr

Re: Guix Home Entertainment SoC Media Server?

[phodina]

Hi Blake,

> Hiya Guix!
>
> I just got a TV and want to put together a little SoC home media server for
>
> it (perhaps with beaglebone black, as that appears to be the recommended
>
> SoC for Guix). Has anyone had any experience with this? Thoughts?
>
> I figure it could be a fun use of `Guix Deploy`, but I've never put
>
> together a SoC media server before, so I'm not sure what packages to
>
> peek at, or what "out of the box" (re: raspbian etc) options are
>
> available.
>
> Seems like this could be some cool shoes for Guix to fill!
>
> ez,
>
> blake

I'd probably recommend something like Raspberry Pi. The latest iteration is 
quite powerful and you can run Kodi there.

There's a patch pending to support this fruit board in Guix :-)

Patches to install guix system on Raspberry Pi [1]

[1] https://lists.gnu.org/archive/html/guix-patches/2021-06/msg01228.html


Petr

Re: guix home .bashrc query

[Paul Jewell]

I have spent some time with this now, and post this for completion 
should anyone else have the same query.


The duplication I saw is exactly as expected. The configuration created 
by the "guix home import" command includes a home-bash-configuration 
section. In this section, there is a field guix-defaults? with defines 
whether the .bashrc should be created with the standard guix content. 
This defaults to #t, and is not changed by guix home import. The "guix 
home import " command also adds a bashrc field which adds the current 
content of .bashrc to the end of the default content. Since I hadn't 
made any changes to my .bashrc from the standard, this gave me the 
appearance of duplication.


If it is appropriate, I would be happy to consider how to adjust the 
manual page to make this clearer and to submit a patch. Of course I 
recognise that the manual pages for guix home are currently under 
development, so perhaps my input wouldn't be so helpful! Perhaps the 
"guix home import" command should not add the content of the .bashrc to 
the default - in other words the output should have (guix-defaults? #f) 
included at the appropriate point?


Thanks to Andrew and the other developers for guix home - I like what I 
see! :)



On 29/12/2021 12:15, Paul Jewell wrote:


On 29/12/2021 12:06, Paul Jewell wrote:
I am starting to work with guix home, and after the simple "guix home 
import" and guix home reconfigure with the created configuration, I 
note that the .bashrc now has the original content from my .bashrc, 
but duplicated, with one exception - the check to see if /etc/bashrc 
is present before sourcing it has been removed. The aliases 
referenced in the configuration file are also added at the bottom (no 
surprise in this case - I should just remove them from the copy of 
.bashrc taken during the import).


Is this duplication a bug, or have I missed something? I can of 
course share the configuration file and the contents of .bashrc if 
that is helpful.


Thanks!



Re-reading what I posted, I think I wasn't clear enough. To be 
absolutely clear - when I say duplicated, I mean the original contents 
of .bashrc are now in the new .bashrc file twice.