Not understanding `Get-DotFiles`

[klauern]

I don't quite understand what the Availability column, and why this doesn't behave similarly to stow:

C:\Users\klauer\dotfiles [arch ≡ +1 ~0 -0 !]
λ  Get-DotFiles

Directory Name Availability State
--------- ---- ------------ -----
bash           NoLogic      NotEvaluated
config         NoLogic      NotEvaluated
emacs          NoLogic      NotEvaluated
git       Git  Available    Installed
hg             NoLogic      NotEvaluated
npm            NoLogic      NotEvaluated
ruby           NoLogic      NotEvaluated
ssh            NoLogic      NotEvaluated
svn            NoLogic      NotEvaluated
tmux           NoLogic      NotEvaluated
utils          NoLogic      NotEvaluated
vim            NoLogic      NotEvaluated
X11            NoLogic      NotEvaluated
zsh            NoLogic      NotEvaluated

Personally, I don't know if it matters for me to have logic for particular components because linking them to my user home directory would effectively be a no-op if I didn't have a component that was useful in Windows. Is there something that Availability does that prevents me from having things like npm, ssh, svn, hg, emacs, etc., work just like stow, and naively link them?

[ralish]

I can see how a simpler and more naive stow-like option would be helpful. I built PSDotFiles with my own dotfiles in mind, and having many different configurations wanted to ensure only the applicable components were symlinked in to avoid "pollution" of my profile directory. That said, for those with a smaller collection of dotfiles or who just want to avoid dealing with matching logic, this makes a lot of sense. It shouldn't be too hard to add, and I've been meaning to clean-up some of the code anyway. Will see what I can do.

[Keshav13142]

I can see how a simpler and more naive stow-like option would be helpful. I built PSDotFiles with my own dotfiles in mind, and having many different configurations wanted to ensure only the applicable components were symlinked in to avoid "pollution" of my profile directory. That said, for those with a smaller collection of dotfiles or who just want to avoid dealing with matching logic, this makes a lot of sense. It shouldn't be too hard to add, and I've been meaning to clean-up some of the code anyway. Will see what I can do.

Hey any updates or workarounds for this issue?
I'm also stuck with the Unavailable Message when I try to install dotfiles for winfetch

[ralish]

@Keshav13142 I'm keen to implement it but am pretty time constrained right now. If you open a separate issues with the relevant output from the install attempt I'm happy to lend a hand.

[bartdorsey]

Is there a way to add our own metadata files somewhere?

[bartdorsey]

Actually I'll share this info for whoever is reading this and trying to figure this out. If you make a "metadata" folder in your dotfiles directory, this will look inside it for custom xml files to determine where to install things. This wasn't obvious to me from reading the docs.

[ralish]

I keep meaning to better document this module but never seem to get around to it. I'm leaving this issue open until I do!

[AdamuAbba]

Actually I'll share this info for whoever is reading this and trying to figure this out. If you make a "metadata" folder in your dotfiles directory, this will look inside it for custom xml files to determine where to install things. This wasn't obvious to me from reading the docs.

Hey thank you so much for this, please could you share a sample of yours ? showing how the xml files should look?

[AdamuAbba]

I keep meaning to better document this module but never seem to get around to it. I'm leaving this issue open until I do!

please could you share a sample of how one of the xml files would look like? i would really appreciate that.

[ralish]

@AdamuAbba You can find several in the metadata directory of this repository, and many more in the metadata directory of my personal dotfiles. You should also take a look at Metadata.sample.xml which provides a detailed sample XML file with comments.