-
Notifications
You must be signed in to change notification settings - Fork 176
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
Verify yadm alt filters #360
Comments
Yes, I like this idea a lot! |
@TheLocehiliosan I made a pr. this is my first contribution here so let me know if I've done something wrong. |
This issue has been labeled as stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
@TheLocehiliosan updated the pr |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Setting up Alts for different systems and environments can get annoying when you don't know what yadm thinks it's installing Alts to. E.g on chroots like termux
Describe the solution you'd like
Would be nice if there was a way of printing the alt variables that yadm detects like
yadm verify os
oryadm verify distro
or something along those lines so I can see what yadm sees and take the guesswork out of it since wsl has proved that what you think is the os is unreliable and turmux has proved the same problem too. It also returns Linux but appears to be something different.Describe alternatives you've considered
I've attempted to run the same calls that yadm claims to run when creating alt symlinks (eg
cat /etc/os-release
sincelsb_release -si
is never installed.) However I'm not getting the symlinks created when using the returned results in my alt filter (egbootstrap.d##o.linux,d.archarm
)Additional context
Would just be nice to verify what yadm is filtering by without trial and error.
The text was updated successfully, but these errors were encountered: