Skip to content
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

stow imposes unnecessarily strict requirements #11

Open
RangHo opened this issue Oct 23, 2022 · 1 comment
Open

stow imposes unnecessarily strict requirements #11

RangHo opened this issue Oct 23, 2022 · 1 comment
Labels
🐛 bug This is broken af

Comments

@RangHo
Copy link
Owner

RangHo commented Oct 23, 2022

Currently, stow is being used to create symbolic links automatically. However, it does create some hassle when there are other symbolic links in the home directory (i.e. WSL and Android).

Some package don't even require stow in the first place, so let's ditch that altogether and make one myself.

It has to be done before December, as I need to set up a fresh system by then.

@RangHo RangHo added the 🐛 bug This is broken af label Oct 23, 2022
@RangHo
Copy link
Owner Author

RangHo commented Dec 18, 2022

Currently, installation of a dotfile package means that the "package manifest" script gets copied to the local dotfile directory. In order to migrate away from stow, I may have to change how this thing works in the first place.

One option is to keep track of the changes to install a package using special commands. It would look something like:

# This package installs a native package named "vim"
native vim

# This package copies the file below from elsewhere
copy ~/.local/bin/awesome-binary

# This package creates a symlink
symlink ~/.config/awesome-binary/config.toml

This should allow uninstallation logic to effectively "undo" any changes made to the system. Dependency management might get even more complex, but I guess I came way too far.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug This is broken af
Projects
None yet
Development

No branches or pull requests

1 participant