Search Criteria
Package Details: arf 0.2.5-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/arf.git (read-only, click to copy) |
|---|---|
| Package Base: | arf |
| Description: | A modern R console |
| Upstream URL: | https://github.com/eitsupi/arf |
| Licenses: | MIT |
| Conflicts: | arf-bin |
| Submitter: | novica |
| Maintainer: | novica |
| Last Packager: | novica |
| Votes: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2026-02-06 12:42 (UTC) |
| Last Updated: | 2026-03-21 12:49 (UTC) |
Dependencies (3)
- glibc (glibc-gitAUR, glibc-eacAUR, glibc-git-native-pgoAUR)
- libgcc (libgcc-snapshotAUR)
- rust (rust-beta-binAUR, rustup-gitAUR, rust-gitAUR, rustup) (make)
Latest Comments
Knotrocket commented on 2026-02-17 14:19 (UTC) (edited on 2026-02-17 14:24 (UTC) by Knotrocket)
I will go ahead and rename my tool's package then but leave the binary name the same for now.
novica commented on 2026-02-17 08:13 (UTC)
Hi. So I am just packaging this tool, and not responsible for the code, and it's original name. I can rename the package, but that may be less convenient for users if they try to find the tool, which is named arf (https://github.com/eitsupi/arf).
Because you are both the developer and packager of arf-git (and it is still early stages) it may make more sense to rename it now and make a suite of packages (-bin, etc).
But as I said before, as you were first, if you prefer to keep the name, no problem, I will figure the steps to rename it, only it will probably be over the weekend.
Knotrocket commented on 2026-02-16 20:52 (UTC)
Hi again. Are you able to confirm if this package could be renamed? I don't mind either way but would like to know so I may upload the first tagged release, otherwise I will go ahead and submit a rename request for arf-git.
Knotrocket commented on 2026-02-09 14:22 (UTC) (edited on 2026-02-09 15:30 (UTC) by Knotrocket)
I added the word "experimental" because the tool was not nearly as robust as I previously thought but I am slowly fixing that. It's also worth noting the tool was prevoiusly named
fzurso I can go back to that or find a different name if needed.novica commented on 2026-02-09 13:56 (UTC)
Hi again. I agree with you about the confusion. You were the first so I have no problem renaming. Are you going to keep working on your tool? The repo page says 'experimental'.
Knotrocket commented on 2026-02-09 13:32 (UTC)
Thanks for the response! The
arfpackage did not exist, onlyarf-gitbecause I did not tag a release for my project yet. I am not asking for a rename but it is a little confusing to end up with a completely different piece of software depending on if the-gitversion is chosen.novica commented on 2026-02-09 07:22 (UTC)
Hi, it is a coincidence. I was working on packaging sever r-language related tools over the past few weeks. And I did my best to check if other packages with same names existed. It may be that when I checked for
arfthe package was not there, or I didn't notice in my search. For those that I noticed same names, I prefixed them withr-.Knotrocket commented on 2026-02-09 01:25 (UTC) (edited on 2026-02-09 01:49 (UTC) by Knotrocket)
Hi, I am curious if it is a coincidence that both this package and arf-bin were published to the AUR just 3 weeks after my package arf-git.