We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've got some requests for getting dracut into the Fedora repository.
Status quo: there is a Copr repository that also provides Fedora packages (cf. link in the README).
Of course, having the package available in the Fedora repository makes sense as this simplifies the deployment of dracut-sshd.
There is also the idea of upstreaming dracut-sshd (cf. issue #8 ), but this likely will take some time as nobody is currently driving this effort.
For an approved Fedora packager, preparing a Fedora package review submission shouldn't take too much time. It basically involves:
Thus, it's considerably less effort than the upstreaming and thus still worth it even if the upstreaming effort continues at some point.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I've got some requests for getting dracut into the Fedora repository.
Status quo: there is a Copr repository that also provides Fedora packages (cf. link in the README).
Of course, having the package available in the Fedora repository makes sense as this simplifies the deployment of dracut-sshd.
There is also the idea of upstreaming dracut-sshd (cf. issue #8 ), but this likely will take some time as nobody is currently driving this effort.
For an approved Fedora packager, preparing a Fedora package review submission shouldn't take too much time. It basically involves:
Thus, it's considerably less effort than the upstreaming and thus still worth it even if the upstreaming effort continues at some point.
The text was updated successfully, but these errors were encountered: