Package Details: rshell 0.0.36-1

Git Clone URL: https://aur.archlinux.org/rshell.git (read-only, click to copy)
Package Base: rshell
Description: A remote shell for working with MicroPython boards
Upstream URL: https://github.com/dhylands/rshell
Keywords: micropython shell
Licenses: MIT
Submitter: n0gg1n
Maintainer: SpotlightKid
Last Packager: SpotlightKid
Votes: 9
Popularity: 0.000000
First Submitted: 2019-05-14 09:03 (UTC)
Last Updated: 2024-12-23 12:58 (UTC)

Latest Comments

1 2 Next › Last »

mags commented on 2024-12-23 19:13 (UTC)

My bad, I was positive someone on IRC told me to do it that way a while back, but looking at the logs I can't find it. Anyway, thanks for maintaining this, cheers.

SpotlightKid commented on 2024-12-23 12:59 (UTC)

@mags: Please read https://wiki.archlinux.org/title/Arch_User_Repository#Updating_packages

But the package needed to be updated anyway, so I just did that.

mags commented on 2024-12-23 01:00 (UTC)

This pkgrel should be bumped to 2 to force a rebuild against python 3.13.

ruahcra commented on 2022-03-23 05:36 (UTC)

Try setting the EDITOR env variable, so then other programs (including rshell) will use your preferred editor.

-e EDITOR, --editor

Specifies the editor to use with the edit command. If no editor is specified, then the following environment variables will be searched: RSHELL_EDITOR, VISUAL, and EDITOR. If none of those environment variables is set then vi will be used.

kearneyBack commented on 2022-03-23 02:52 (UTC)

I install it from AUR 0.0.31-1 successfully. Connect and listdir fine. When I try to edit, it turns out a error: sh vi command not found.

I use Manjaro and I do not install vi. Then I think maybe this is a reason. Then I install vi(1:070224-5) and edit file again. It works. Then I think vi should be its depends.

n0gg1n commented on 2020-05-09 08:09 (UTC)

currently not using arch any more. Would be nice if someone could adopt the package maintenance.

SpotlightKid commented on 2020-05-08 12:08 (UTC)

@XenGi: each entry point command line script imports pkg_resources.

XenGi commented on 2020-05-08 10:25 (UTC) (edited on 2020-05-08 10:26 (UTC) by XenGi)

Seems like I never came back to this. You don't have to rename the package. It's completely fine like it is. The Arch guidelines (https://wiki.archlinux.org/index.php/Python_package_guidelines#Package_naming) state that a python library should be named python-pkg and a tool written in python like rshell should be just called pkg without the prefix. Sorry for the confusion.

SpotlightKid: Are you sure about this? I don't see a reason why this would be necessary. Can you point us to some docs that describe that behaviour?

SpotlightKid commented on 2020-05-07 14:12 (UTC)

Please move python-setuptools from makedepends into depends.

Every Python package, which installs scripts via setuptools entry points, as rshell does too, needs python-setuptools as a run-time dependency, i.e. in depends, not only at build time (i.e. makedepends).

n0gg1n commented on 2020-01-23 08:20 (UTC)

Renaming packages is actually not that easy...is that name too confusing?

1 2 Next › Last »