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

PKGBUILD: Drop .install script #310

Merged
merged 1 commit into from
Oct 6, 2024
Merged

PKGBUILD: Drop .install script #310

merged 1 commit into from
Oct 6, 2024

Conversation

1Naim
Copy link
Member

@1Naim 1Naim commented Oct 6, 2024

The .install script we had all this time for the rt kernel was never ran on upgrades and installs due to being "sourced" incorrectly in the PKGBUILD. It should have been "sourced" in install= instead for it to be ran. However, sourcing it this way poses a few problems:

  1. If we add install= along in the case statements for cpusched types, the post install script will be ran for each kernel package installed.
  2. We could add it to the _package() function for the kernel, but this needs if statements so that its ran on the correct kernel flavour (clutter IMO). Adding it only for the rt kernel in case of linux-cachyos-rt.install would make its PKGBUILD inconsistent with others (a case can be made that the default kernel is now inconsistent with the other PKGBUILDs, but the default kernel in nature will always be subject to some changes that will not be seen by the other kernel variants)

Due to the aforementioned problems, drop the post install scripts. This decision was also largely in part of the low usage count of the rt kernel. We will also be removing linux-cachyos.install anyway as it is only a temporary addition to smooth out migration.

The .install script we had all this time for the rt kernel was never ran on upgrades and installs due to being "sourced"
incorrectly in the PKGBUILD. It should have been "sourced" in `install=` instead for it to be ran. However, sourcing
it this way poses a few problems:

1. If we add `install=` along in the case statements for cpusched types, the post install script will be ran
for each kernel package installed.
2. We could add it to the _package() function for the kernel, but this needs if statements so that its ran on the
correct kernel flavour (clutter IMO). Adding it *only* for the rt kernel in case of `linux-cachyos-rt.install` would
make its PKGBUILD inconsistent with others (a case can be made that the default kernel is now inconsistent with the
other PKGBUILDs, but the default kernel in nature will always be subject to some changes that will not be seen by the other
kernel variants)

Due to the aforementioned problems, drop the post install scripts. This decision was also largely in part of the low
usage count of the rt kernel. We will also be removing `linux-cachyos.install` anyway as it is only a temporary addition
to smooth out migration.

Signed-off-by: Eric Naim <[email protected]>
@1Naim 1Naim requested a review from ptr1337 October 6, 2024 19:24
@ptr1337 ptr1337 merged commit 82a8dc3 into master Oct 6, 2024
2 checks passed
@ptr1337 ptr1337 deleted the drop-post-install branch October 6, 2024 19:27
@ventureoo
Copy link
Member

the post install script will be ran for each kernel package installed.

Why? I don't get why this has to be called for every kernel. The .install scripts are per-package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants