Still deprecate install.sh and update.sh anyway; Tidier structure

This commit is contained in:
clsty
2025-10-31 09:11:03 +08:00
parent f01a2a06b5
commit d36966e2d7
6 changed files with 12 additions and 54 deletions
+1 -1
View File
@@ -13,7 +13,7 @@ The mechanism is introduced by [Makrennel](https://github.com/Makrennel) in [PR#
Why is this awesome?
- It makes it possible to control version since some packages may involve breaking changes from time to time.
- It makes the dependency trackable for package manager, so that you always know why you have installed some package.
- As a result, it enables a workable `uninstall.sh` script.
- As a result, it enables a workable uninstall process.
The PKGBUILDs contains two forms of dependencies:
- Package name written in dependencies, like a "meta" package.
+1 -1
View File
@@ -477,7 +477,7 @@ if [[ "${SKIP_NOTICE}" == false ]]; then
log_warning "THIS SCRIPT IS NOT FULLY TESTED AND MAY CAUSE ISSUES!"
log_warning "It might be safer if you want to preserve your modifications and not delete added files,"
log_warning " but this can cause partial updates and therefore unexpected behavior like in #1856."
log_warning "In general, prefer install.sh for updates."
log_warning "In general, prefer ./setup install for updates."
safe_read "Continue? (y/N): " response "N"
if [[ ! "$response" =~ ^[Yy]$ ]]; then