Update documentation with an installation shell script

[psychoslave]

The installation process could be given as a single shell snippet that can be copied and pasted:

# chose the path to get the code
cd $PROJECTS_PATH
# Clone the repository:
git clone https://github.com/projecthamster/hamster-shell-extension.git
# Make sure you are on the development branch:
git checkout develop
# Build a fresh distribution package:
make dist
# install the extension
mkdir -p ~/.local/share/gnome-shell/extensions/[email protected] && tar xzf [email protected] -C ~/.local/share/gnome-shell/extensions/[email protected] 

thus said, it doesn't make appear hamster appear in my tweak application on Fedora 28, so maybe last instruction is wrong.

[elbenfreund]

Hi. Whats your usecase for this?

In general, extensions.gnome.org is supposed to be the singular distribution channel for extensions.
Now, for testing purposes as well as due to the current delay in getting the extension through EGO review, we do already provide a convenient way to package and install the extension. You can find more about the details in the Readme.

The make file does not provide a way to take the last step of "install extension on my system". This is a deliberate choice. Users should use the mechanisms provided by the tweeak tool instead of a script that makes asumptions about where the extension should live.

[psychoslave]

Thank you @elbenfreund for your reply. On a bright new Fedora 29, I wasn't able to install the extension at all, whether through the gnome extension website or by cloning the repo. Tweak seems to no longer provide a button to select a local archive to install.

It's fine to want to go through the whole official process, but if the result is an extension that can't be installed at all by simply following a provided documentation, it's less relevant IMO.

Cheers

[ederag]

Same on openSUSE.
Had to install the hamster-time-tracker,
that installed also gnome-shell-extension-hamster-time-tracker,
and gnome-tweak-tool.
Then tweaks (not "tweaktool" as stated in the README) became available in the Activities,
and the extension was in there ready to be checked out,
but there is nothing "at the bottom of the extensions tab" to install from a file.