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

New package: tuxedo-keyboard-dkms-3.0.9 #36465

Closed
wants to merge 2 commits into from
Closed

New package: tuxedo-keyboard-dkms-3.0.9 #36465

wants to merge 2 commits into from

Conversation

QuadPiece
Copy link
Contributor

This is my first void package, please be strict.

DKMS modules developed by Tuxedo Computers for their laptops.
They provide drivers for many device-specific things such as keyboard backlight, fan control and fn-keys.

Due to the nature of Tuxedo laptops, this module usually also works on other laptops using the same Clevo or TongFang designs.

Testing the changes

New package

Local build testing

  • I built this PR locally for my native architecture (x86_64-musl)

@paper42 paper42 added the new-package This PR adds a new package label Apr 2, 2022
@QuadPiece
Copy link
Contributor Author

I managed to break this PR because I forgot to branch my changes. Will resubmit properly.

@QuadPiece QuadPiece closed this Apr 13, 2022
@apprehensions
Copy link
Contributor

i would always suggest to make a new package under a different branch.
for example i fork void-packages and don't touch the master branch.
i make a new branch from master named after the package i would want to submit.

it is also generally unrecommended to make a new New package PR after you have already made one, but seems somethign went wrong so..

@QuadPiece
Copy link
Contributor Author

Yes, I thought I made an added-<package name> branch. But apparently I didn't and accidentally did some other stuff to master it was my mistake.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-package This PR adds a new package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants