Improved descriptions. Self-describing patch-file name.
OBS-URL: https://build.opensuse.org/package/show/utilities/homeshick?expand=0&rev=2
This commit is contained in:
parent
cc3dc74d98
commit
443d806ce7
@ -34,17 +34,15 @@ printf '\nsource "/usr/share/homeshick/homeshick.sh"' >> $HOME/.bashrc
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
## Hackers and developers
|
||||
## Multiple installations
|
||||
|
||||
The default method of installing homeshick is for each user to make a private
|
||||
clone of the upstream repository from Github. For users that want to modify the
|
||||
implementation, and maybe make contributions to homeshick, that remains the way
|
||||
to go about it.
|
||||
clone of the upstream repository from Github. For users wanting to modify the
|
||||
implementation, or to make contributions to homeshick, that remains the way to
|
||||
go about it.
|
||||
|
||||
A git clone and this package can co-exist. Assuming that the setup scripts have
|
||||
been sourced, as instructed above, the environment variable `HOMESHICK_DIR` can
|
||||
be used to control which instance of homeshick is run, the default being the
|
||||
instance installed by this package.
|
||||
This package can co-exist with git clone(s) of homeshick. Assuming that a setup
|
||||
script from this package has been sourced, as instructed above, the environment
|
||||
variable `HOMESHICK_DIR` can be used to control which instance of homeshick is
|
||||
run, the default being the instance installed by this package.
|
||||
|
||||
|
@ -30,7 +30,7 @@ Group: Productivity/File utilities
|
||||
Url: https://github.com/andsens/homeshick
|
||||
Source0: https://github.com/andsens/homeshick/archive/%{git_sha1}.zip
|
||||
Source1: README-openSUSE.md
|
||||
Patch0: homeshick.patch
|
||||
Patch0: default-location.patch
|
||||
BuildRequires: expect
|
||||
BuildRequires: git >= 1.5
|
||||
BuildRequires: iputils
|
||||
@ -46,21 +46,15 @@ BuildRequires: fish
|
||||
%endif
|
||||
|
||||
%description
|
||||
In Unix, configuration files are king. Tailoring tools to suit your needs
|
||||
through configuration can be empowering. An immense number of hours is spent
|
||||
on getting these adjustments just right, but once you leave the confines of
|
||||
your own computer, these local optimizations are left behind.
|
||||
Homeshick is a tool for users to manage configuration files, also known as
|
||||
dotfiles. A set of dotfiles is stored in a git repository. Standard git
|
||||
push/pull commands are used to synchronize a dotfile repository between user
|
||||
accounts and/or machines. Multiple git repositories can be managed
|
||||
independently. For example, this allows installing large external frameworks
|
||||
(such as oh-my-zsh, or a multitude of emacs or vim plugins) alongside personal
|
||||
dotfiles without clutter.
|
||||
|
||||
By the power of git, homeshick enables you to bring the symphony of settings
|
||||
you have poured your heart into with you to remote computers. With it you can
|
||||
begin to focus even more energy on bettering your work environment since the
|
||||
benefits are reaped on whichever machine you are using.
|
||||
|
||||
However bare bones these machines are, provided that at least bash 3 and git
|
||||
1.5 are available you can use homeshick. homeshick can handle multiple dotfile
|
||||
repositories. This means that you can install larger frameworks like oh-my-zsh
|
||||
or a multitude of emacs or vim plugins alongside your own customizations
|
||||
without clutter.
|
||||
See also: https://dotfiles.github.io/
|
||||
|
||||
Packaged revision: %{git_sha1}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user