On Sat, 16 May 2020 at 00:49, José Abílio Matos wrote:
>
> If we take the example from python where I have installed versions from python
> 3.4 to 3.9 (that is yet in alpha stage).
>
> # rpm -qf /usr/bin/python3.?
> python34-3.4.10-10.fc32.x86_64
> python35-3.5.9-1.fc32.x86_64
> python36-3.6.10-2.
On Friday, 15 May 2020 11.33.26 WEST Iñaki Ucar wrote:
> The rationale behind the user settings is that the user dir is not
> controlled by the system, so versioning it is the only way to avoid
> breakage. For the system library, there are better tools to prevent
> that.
Do you know the difference
On Fri, 15 May 2020 at 11:58, José Abílio Matos wrote:
>
> On Thursday, 14 May 2020 23.58.02 WEST Iñaki Ucar wrote:
> > But we still have to rebuild the packages anyway, and this setup
> > doesn't force us to actually rebuild them, nor the user to update
> > them. So a user could end up with R maj
On Thursday, 14 May 2020 23.58.02 WEST Iñaki Ucar wrote:
> But we still have to rebuild the packages anyway, and this setup
> doesn't force us to actually rebuild them, nor the user to update
> them. So a user could end up with R major.minor and a bunch of
> packages installed in some major.minor-1
On Tue, 12 May 2020 at 12:13, Tom Callaway wrote:
>
> Okay, I'm convinced.
>
> https://github.com/rpm-software-management/R-rpm-macros/pull/1
>
I merged the PR and pushed it to dist-git as well. I have not built
anything though, since as I mentioned in the PR, I think builds should
be done in a s
