Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't allow previously installed packages to become AUR packages #2468

Open
Rosentti opened this issue Jul 2, 2024 · 0 comments
Open

Don't allow previously installed packages to become AUR packages #2468

Rosentti opened this issue Jul 2, 2024 · 0 comments
Labels
Status: Discussion Open Topic is being considered and open for discussion Type: Feature Request

Comments

@Rosentti
Copy link

Rosentti commented Jul 2, 2024

Is your feature request related to a problem? Please describe.

The electron meta-package depends on electronXX, where XX is the current version. The old package however doesn't get removed as electron updates, and old versions of electron eventually get removed from the repos. This allows someone to make an AUR package with the old name, which yay then picks up on and downloads.
This seems a bit hazardous, and yay should probably not allow a package to switch from the repos to the AUR without asking the user first.
I'm not sure if this is what caused electron25 to be installed for me, but I don't strictly remember downloading it myself...

Describe the solution you'd like

Add a prompt to ask the user if this is indeed what they wanted to happen.

Describe alternatives you've considered

Completely blocking the download of "relocated" packages.

Additional context

I first recognized this when yay started downloading chromium sources during a system update and I was wondering why, then a couple
lines above it said Cloning into .cache/yay/electron25/chromium-mirror
This might also be my fault for not looking through the updatable AUR packages more carefully.

@Rosentti Rosentti added Status: Discussion Open Topic is being considered and open for discussion Type: Feature Request labels Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Discussion Open Topic is being considered and open for discussion Type: Feature Request
Projects
None yet
Development

No branches or pull requests

1 participant