Edd Salkield

I haven't had the time to look further, but I intend to try and create an Alpine package for this project. I'll get back to you with more information as...

TLDR: turns out it's a problem with upstream rust that's known about and being worked on. For now, this can be fixed by explicitly specifying no static linking with `RUSTFLAGS="-C...

Perhaps if the [documentation](https://elkowar.github.io/eww/eww.html) is getting updated with this temporary fix, we could also update it to list `musl` as a valid alternative to `glibc` in the packages list?

I have forked the project and [converted it to python3](https://github.com/eddsalkield/analyzeMFT3). This should work for your use case.

You can find it packaged at the [PyPi](https://pypi.org), as [analyzeMFT3](https://pypi.org/project/analyzeMFT3).

Unfortunately I do not intend to continue the python3 version of the project, as I no longer use this utility.

Thanks for the mention. I have modified the README to make it clear that my fork is unmaintained.

A few things to discuss: expanding environment variables in the `target` manifest file is currently handled safely by `envsubst`, which adds a dependency on GNU `gettext`. I believe this is...

There's a bit of a debate to be had as to where _dotfiles_ should go in `$XDG_CONFIG_HOME/rcm/dotfiles` or `$XDG_DATA_HOME/rcm/dotfiles`. I think we can safely rule out `$XDG_DATA_HOME/dotfiles`, as people would...

I think this is almost right, although we really should incorporate @mat-m's approach of separating config files from data. The logical flow would be as follows: The `.rcrc` file should...