-
Notifications
You must be signed in to change notification settings - Fork 484
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
Move from a base group to a base meta package #1976
Labels
Comments
I just checked with a dummy package and a dummy repo:
|
lazka
added a commit
to lazka/MSYS2-packages
that referenced
this issue
May 27, 2020
This is meant as a replacement for the base group and contains the same packages. If a user has the base package installed (the installer will do this in the future) then we can add new packages to the base and users with existing installations will get those packages installed automatically. This follows what Arch did last year: https://www.archlinux.org/news/base-group-replaced-by-mandatory-base-package-manual-intervention-required/ See msys2#1976
Merged
Thanks for testing. I've created #1979 |
lazka
added a commit
to lazka/MSYS2-packages
that referenced
this issue
May 28, 2020
This is meant as a replacement for the base group and contains the same packages. If a user has the base package installed (the installer will do this in the future) then we can add new packages to the base and users with existing installations will get those packages installed automatically. This follows what Arch did last year: https://www.archlinux.org/news/base-group-replaced-by-mandatory-base-package-manual-intervention-required/ See msys2#1976
lazka
added a commit
to lazka/MSYS2-packages
that referenced
this issue
May 28, 2020
This is meant as a replacement for the base group and contains the same packages. If a user has the base package installed (the installer will do this in the future) then we can add new packages to the base and users with existing installations will get those packages installed automatically. This follows what Arch did last year: https://www.archlinux.org/news/base-group-replaced-by-mandatory-base-package-manual-intervention-required/ See msys2#1976
lazka
added a commit
to lazka/MSYS2-packages
that referenced
this issue
May 28, 2020
This is meant as a replacement for the base group and contains the same packages. If a user has the base package installed (the installer will do this in the future) then we can add new packages to the base and users with existing installations will get those packages installed automatically. This follows what Arch did last year: https://www.archlinux.org/news/base-group-replaced-by-mandatory-base-package-manual-intervention-required/ See msys2#1976
lazka
added a commit
to lazka/MSYS2-packages
that referenced
this issue
May 28, 2020
This is meant as a replacement for the base group and contains the same packages. If a user has the base package installed (the installer will do this in the future) then we can add new packages to the base and users with existing installations will get those packages installed automatically. This follows what Arch did last year: https://www.archlinux.org/news/base-group-replaced-by-mandatory-base-package-manual-intervention-required/ See msys2#1976
lazka
added a commit
to lazka/MSYS2-packages
that referenced
this issue
May 28, 2020
This is meant as a replacement for the base group and contains the same packages. If a user has the base package installed (the installer will do this in the future) then we can add new packages to the base and users with existing installations will get those packages installed automatically. This follows what Arch did last year: https://www.archlinux.org/news/base-group-replaced-by-mandatory-base-package-manual-intervention-required/ See msys2#1976
Alexpux
pushed a commit
that referenced
this issue
May 29, 2020
* Add a base package This is meant as a replacement for the base group and contains the same packages. If a user has the base package installed (the installer will do this in the future) then we can add new packages to the base and users with existing installations will get those packages installed automatically. This follows what Arch did last year: https://www.archlinux.org/news/base-group-replaced-by-mandatory-base-package-manual-intervention-required/ See #1976 * base: explicitly depend on zstd and wget They get already pulled in through pactoys, but this makes it explicit
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See https://lists.archlinux.org/pipermail/arch-dev-public/2019-January/029435.html and https://wiki.archlinux.org/index.php/Meta_package_and_package_group
By having a package we can easily add/remove packages from the base system.
For example we could split pacman and pacman-contrib (which atm get built together, but contrib builds against the previously installed one) without users losing pacman-contrib.
Open questions:
pacman -S base
if we have both a group and a package named "base"?The text was updated successfully, but these errors were encountered: