ca-certificates: just call update-ca-trust in the install script #3492
Conversation
currently the install script is more or less a copy of update-ca-trust, so to simplify things just call update-ca-trust in the install script
|
wonder why it was done that way to begin with... maybe something to do with when it's invoked as an install script? |
The rest of that commit suggests that something happen with /bin -> /usr/bin like changes. |
|
The only reason I can think of is pacman installing to a different root, but it still shouldn't make a difference due to chroot, see https://bbs.archlinux.org/viewtopic.php?pid=913891#p913891 |
|
OK, the 'different root' install for making the installer was what I was most concerned about, since I remember this install script breaking in the past and causing issues. Probably would cause more issues now than before, with more of the extraneous first run actions being removed from filesystem. |
|
I've added an optional input flag to the https://github.com/msys2/msys2-installer/actions/workflows/build.yml workflow, so we can test creating the installer from staging. edit: that turned out to be buggy... so reverted |
currently the install script is more or less a copy of update-ca-trust, so to simplify things just call update-ca-trust in the install script