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

Force re-running of installation scripts #7

Open
samatjain opened this issue May 8, 2014 · 4 comments
Open

Force re-running of installation scripts #7

samatjain opened this issue May 8, 2014 · 4 comments

Comments

@samatjain
Copy link

A '--force' flag for install, or something similar, that forces dots to rerun all installation scripts (*.install files).

At the moment, dots only will execute an installation script if the corresponding configuration file has changed.

@evanpurkhiser
Copy link
Owner

How about -r for --reinstall. Which will force reinstalling of the selected configuration files (even if they haven't changed). Which will also run the install scripts.

Or do you think it should be more fine grained where we differentiate between reinstalling configuration files, and re-running the install scripts?

@samatjain
Copy link
Author

I don't think there's a need to differentiate—a "--reinstall' option sounds good to me.

@countsudoku
Copy link

I would like to propose another enhancement: *.update scrips (or something similar), which get executed every time dots install is been executed whether or not the config file have changed. I would like to use this, to sync some dconf/gsettings config between my computers.

What do you think about this proposal?

@evanpurkhiser
Copy link
Owner

@countsudoku I'm definitely open to something like that.

I've been quite busy for the past few months and unforunately have not had the time to work on a refactored version of dots as I've briefly outlined in GH-20. So I'm not sure I'll have time to implement it (though it should be very straight forward, and thus I would be open to a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants