Search Criteria
Package Details: r-swirl 2.4.4-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/r-swirl.git (read-only, click to copy) |
---|---|
Package Base: | r-swirl |
Description: | Platform for learning (and teaching) statistics and R simultaneously and interactively |
Upstream URL: | https://github.com/swirldev/swirl |
Licenses: | GPL |
Submitter: | FFY00 |
Maintainer: | None |
Last Packager: | FFY00 |
Votes: | 1 |
Popularity: | 0.000000 |
First Submitted: | 2019-05-10 11:05 (UTC) |
Last Updated: | 2019-07-17 13:38 (UTC) |
Latest Comments
FFY00 commented on 2020-03-11 15:03 (UTC) (edited on 2020-04-19 15:57 (UTC) by FFY00)
I never said the
gcc
package is mandatory to build packages. What I said is that thegcc
is provided bybase-devel
and so it shouldn't be listed inmakedepends
. When you build packages, you are expected to havebase-devel
installed, just like you are expected to havebase
installed in an Arch Linux installation. This is nothing to agree or disagree on, these are distribution guidelines.Regarding the second point, I never said that you should fetch
master
! You should fetch the desired version of the package, but from the upstream. CRAN is the official R package repository, but is not the official upstream for the projects. The upstream is where the projects are developed, which is not CRAN. Fetching the packages from the upstream has several benefits: it's less likely that the sources have been tampered with, sometimes there are GPG signatures available (could be via signed commits/tags), usually it's more clear on what is included in the source, etc.dviktor commented on 2020-03-11 14:42 (UTC) (edited on 2020-03-11 14:47 (UTC) by dviktor)
I disagree with you.
gcc
dependency is not mandatory for all packages. Some AUR or even official packages can build themselves without GCC suite or any compilers at all. Hence a lot of packages which actually needgcc
as part of building process claims it asmakedepends
explicitly.Also I can't agree with second point. CRAN is official R packages repository and provides quite stable releases. It's not 3rd-party place! Many R developers maintains separate repo such as GitHub, GitLab etc for current development but eventually upload final versions to the CRAN. Moreover according to this VCS and stable packages differ from each other. Git versions of packages tracks
master
branch which could be quite unstable so there are a lot of examples in AUR when the same package exists in two forms: stable and VCS (with-git
suffix). It's common practice. Even you have such example: osmo-fl2k and osmo-fl2k-git. So my suggestion is to have both versions ofswirl
package.FFY00 commented on 2020-03-11 13:29 (UTC) (edited on 2020-03-11 13:30 (UTC) by FFY00)
The R packaging guidelines in the Wiki are currently wrong, and it seems like that you were thhe one that modified them. gcc is part of base-devel which is expected to be installed when building packages, hence it is not needed to be listed in the make dependencies. I removed that entry from the wiki.
It is always preferred to fetch the source from the upstream instead of a 3-rd party repo, like CRAN. There is absolutely nothing wrong with the current PKGBUILD.
I can add you as a co-maintainer if want to bump the pkgrel but please do not make significant changes to the PKGBUILD without contacting me. Let me know if you want.
dviktor commented on 2020-03-11 11:25 (UTC) (edited on 2020-03-11 11:26 (UTC) by dviktor)
Please move to CRAN build or rename and rework current
PKGBUILD
to be compliant with Package Guidelines. You can user-metadynminer-git
andr-rustinr-git
as examples