Conditional targets using ENV or hostname

[MacDefender]

Is it possible to extend the current conditional target _linux _macos with an additional one like #myPC or #RPi using a string placed in an ENV var like TUCKR_SUBGROUP and if that is not found the hostname like uname -n or similar?

I would like to have a setup script that can just do a tuckr add whatever and depending on the current computer a different file gets deployed. As all of these are macos the current _target won't work. Setting up a different ENV var would have the benefit to not only use this for different computers but also different styles like setting TUCKR_SUBGROUP to "full_colors" or similar and automatically have other configs linked (maybe even auto checked after something like tuckr recheck * or similar).

I currently checked many dotfile managers and in my opinion tuckr could become one of the best options.

[RaphGL]

So I've thought about it, I think putting hostnames into file names might not be a good idea. With environment variables at least I can always just tell that it should be there and warn the user whenever they try to add a dotfile that needs this env var. With hostnames I can never assume that it ought to be there so I cannot tell you that your config is broken because you changed your hostname.

There's no good way of doing this currently and I can't really think of an approach that I like, what I could think of right now is:

• Hooks approach (a bit finicky)
  Use a hook that sets up the system specific stuff and store them inside the hook directory so that every time you run tuckr set it gets properly deployed/updated

• Dotfile group approach but there's a caveat*
  Create separate groups for each system, you can name them group#host or whatever you want and then use the script to add them after adding everything else with tuckr set \*. You can do this because tuckr won't ever symlink groups that are in conflict when you when you use * it will just ignore the conflicting groups until you manually add them yourself like tuckr set group#pc

* there's a bug where if you have 2 groups sharing a directory that doesn't exist, tuckr won't create the directory so that it can share it, it will just symlink one into the other. This is something I need to get around to fixing but I'll to do a fairly big refactor to integrate it, in practice this bug is not very common so I've been putting it off while I work on other stuff. The short-term fix would be for you to just create said directory yourself before adding.

I currently checked many dotfile managers and in my opinion tuckr could become one of the best options.

Thanks :)
I've managed to go pretty far with the group concept, but there's definitely some missing features and bugs.

[MacDefender]

I currently use the group zsh#myMac approach but this way I also have to create a different deploy script for each host. Not a big problem and the same as with stow but I thought it would be great to have tuckr detect if there is an ENV var like SUBGROUP set. If not just behave as currently but if this is set and a group like zsh should be added first check if zsh#SUBGROUP exists. If yes use this folder and if not just check if a global zsh folder without # exists just as it's currently done. If the user already asked for a zsh#whatever just take that ignoring the ENV.
This way it won't break any existing installations but would allow for easy addition of host specific folders with all the same group name.
So the only difference would be to check if the user asked for a group with a # char and if so take the complete string as folder name as it's currently done. If there is no # included check if the ENV var is set and if so check if a folder with that #ENV exists. If yes choose this and if not just check for the requested group name like zsh.
In the future it might even be possible to allow a global zsh group and additional zsh#ENV versions that both be combined when linking while the #ENV version has a higher priority when a file exists in both folders.
I also would prefer the ENV var over a hostname as this would allow for config changes like ENV=dark or ENV=light. And in the future (a few years from now) maybe even multiple ENVS=thisMac,dark,noServers,.. and all the corresponding group#env folders are combined. Just some ideas for the future to make tuckr the best dotfile manager out there while still very easy to use.
Absolutely no priority as manual using zsh#mymac currently works just fine.

Any thoughts about adding ko-fi page or buymeacoffee link to the github profile?

[RaphGL]

Maybe we could create "custom conditional groups"
They would have to be _#target suffixed that way I can check for the # in there and give it a higher priority than every other group. I could then hint to the user "hey, these custom conditional groups are available and can be used". I am wondering though, should they be environment variables like TUCKR_CUSTOM_ENABLED_TARGETS with comma separated values or if they should just be a flag like in GCC --target=mac,pc whatever.

Any thoughts about adding ko-fi page or buymeacoffee link to the github profile?

I don't have anything set up yet. The way I have my bank account set up right now it cannot receive international payments either so I would have to first go and have my account properly set up before I can receive donations.

[MacDefender]

I would prefer the environment variables as this could be set up once with nix/nix-darwin and then every tuckr add command after that would know that this is _#myMac. This would allow for the same install script on all hosts. But having an additional option flag available for other users that don't use environment variables or maybe even to just try some other targets beside those set in env would be great.