[RFC] xtools: add xtools-minimal subpackage#37826
Merged
classabbyamp merged 1 commit intovoid-linux:masterfrom Jul 7, 2022
Merged
[RFC] xtools: add xtools-minimal subpackage#37826classabbyamp merged 1 commit intovoid-linux:masterfrom
classabbyamp merged 1 commit intovoid-linux:masterfrom
Conversation
Member
|
Why not make a proper subpackage and let xtools depend on xtools-live? |
Member
Author
|
Should've done that in the first place. Also found that several tools that use git can function without it (sans auto-detecting void-packages), but that seems like an acceptable compromise for a live environment, and if the user is downloading void-packages in live for whatever reason, they'll need to install git anyways. |
classabbyamp
changed the title
leahneukirchen
approved these changes
Jul 5, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Testing the changes
I tested the changes in this PR: YES
Not too sure about this approach, it's a bit clunky, and leaves non-included tools in the manpage.
Should the subpackage be named as such or something else?
is this list of tools a good selection? I took all the ones that aren't related to packaging and don't need git (the largest dependency by far)
see also: