We started using those in runtime and in test suite. Also update readme.
Details
- Reviewers
mkrizek - Group Reviewers
libtaskotron - Commits
- rLTRN4a1a6d69b67a: spec: add missing dep on sudo
not tested
Diff Detail
- Repository
- rLTRN libtaskotron
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Yes, but I don't think that really matters, because the package deps must list everything needed. I guess coreutils dep could have some exception (it's really really basic), but I quickly searched packaging guidelines and didn't find anything about it.
Then we need to include kernel into the spec file. On more serious note, I can't imagine use case when one would install libtaskotron on a system without dnf, sudo or coreutils. But if you think this is needed, I don't really care that much.
Nope. We can run in a docker, without kernel.
On more serious note, I can't imagine use case when one would install libtaskotron on a system without dnf, sudo or coreutils.
Just try dnf remove sudo. No broken deps for me, just this single package removed. I can imagine there can be ultimately stripped systems without this package (or somebody being paranoid).
But if you think this is needed, I don't really care that much.
Realistically, probably it isn't. But it should be there. That's packaging.
Also, it helps folks from other distributions. It's easier to see what the "assumed dependencies" are (which might be different in different distributions).
Just try dnf remove coreutils.
But if you think this is needed, I don't really care that much.
Realistically, probably it isn't. But it should be there. That's packaging.
Also, it helps folks from other distributions. It's easier to see what the "assumed dependencies" are (which might be different in different distributions).
Then, look at your readme.rst change, you instruct user to do:
sudo dnf install dnf
and
sudo dnf install sudo.