Automate yum repository install #20895

Closed
Tyriar opened this Issue Feb 19, 2017 · 6 comments

Comments

Projects
None yet
3 participants
@Tyriar
Member

Tyriar commented Feb 19, 2017

#229

We would like the yum repository to get installed automatically when you install the .rpm package, when I tried to do this however I ran into problems with rpm being locked in the post script of the .rpm package. Chrome manages to do this somehow.

@iavael

This comment has been minimized.

Show comment
Hide comment
@iavael

iavael Feb 19, 2017

Chrome manages to do this somehow.

Chrome manages to do this very bad. It ignores user configuration and enforces its own on every update of chrome itself. It's just horrible.

iavael commented Feb 19, 2017

Chrome manages to do this somehow.

Chrome manages to do this very bad. It ignores user configuration and enforces its own on every update of chrome itself. It's just horrible.

@iavael

This comment has been minimized.

Show comment
Hide comment

iavael commented Feb 19, 2017

If you want to make repo configuration easier to end user, create separate package (e.g. vscode-release) with it like rpmfusion does (https://pkgs.rpmfusion.org/cgit/nonfree/rpmfusion-nonfree-release.git/tree/ and https://pkgs.rpmfusion.org/cgit/free/rpmfusion-free-release.git/tree/)
Or like your colleagues do https://packages.microsoft.com/yumrepos/microsoft-rhel7-prod/packages-microsoft-prod-1.0-1.el7.noarch.rpm

@Tyriar

This comment has been minimized.

Show comment
Hide comment
@Tyriar

Tyriar Feb 20, 2017

Member

@iavael thanks for the feedback. It's not clear to me what rpmfusion and microsoft-prod do?

Also what user configuration in particular does Chrome's route ignore?

Member

Tyriar commented Feb 20, 2017

@iavael thanks for the feedback. It's not clear to me what rpmfusion and microsoft-prod do?

Also what user configuration in particular does Chrome's route ignore?

@LenzGr

This comment has been minimized.

Show comment
Hide comment
@LenzGr

LenzGr Feb 20, 2017

It would be nice if the public GPG key and .repo file would be available in packaged form for download from the yum repository directly.

Since RPM/yum/dnf are capable of installing RPMs via http, the installation is as simple as running rpm -i https://packages.microsoft.com/yumrepos/vscode/vscode-release.rpm, followed by ayum/dnf update ; yum/dnf install code

LenzGr commented Feb 20, 2017

It would be nice if the public GPG key and .repo file would be available in packaged form for download from the yum repository directly.

Since RPM/yum/dnf are capable of installing RPMs via http, the installation is as simple as running rpm -i https://packages.microsoft.com/yumrepos/vscode/vscode-release.rpm, followed by ayum/dnf update ; yum/dnf install code

@iavael

This comment has been minimized.

Show comment
Hide comment
@iavael

iavael Feb 20, 2017

@Tyriar

It's not clear to me what rpmfusion and microsoft-prod do?

These packages provide GPG public key for repo and repo-file itself. They update rarely (almost never), so that user's configuration in /etc/yum.repos.d is not violated on every update of software from these repos.

Also what user configuration in particular does Chrome's route ignore?

It ignores if chrome repo is already described in another repo file (e.g. if user tries to have consistend naming of his/her repo files) and creates second entry with the same repo.

iavael commented Feb 20, 2017

@Tyriar

It's not clear to me what rpmfusion and microsoft-prod do?

These packages provide GPG public key for repo and repo-file itself. They update rarely (almost never), so that user's configuration in /etc/yum.repos.d is not violated on every update of software from these repos.

Also what user configuration in particular does Chrome's route ignore?

It ignores if chrome repo is already described in another repo file (e.g. if user tries to have consistend naming of his/her repo files) and creates second entry with the same repo.

@vscodebot

This comment has been minimized.

Show comment
Hide comment
@vscodebot

vscodebot bot Dec 22, 2017

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that have been on the backlog for a long time but have not gained traction: We look at the number of votes the issue has received and the number of duplicate issues filed. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

vscodebot bot commented Dec 22, 2017

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that have been on the backlog for a long time but have not gained traction: We look at the number of votes the issue has received and the number of duplicate issues filed. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this Dec 22, 2017

@Microsoft Microsoft locked and limited conversation to collaborators Feb 5, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.