Consider an installation that would allow git pulling for new changes and allow you to keep custom additions

[travisnewman]

A problem with the installation method is that you need to re-download each time and if you've made custom changes they will get overwritten when copying the new usercrhome.

Using imports you can keep multiple styles that are easily swappable, easily upgradable, and you can keep your custom styles between all of them.

For example, please see how this project works:
https://github.com/ideaweb/firefox-safari-style

[ctrlcmdshft]

This would be a great to make updating much easier

[ghost]

The installer script on the master branch is just a pseudoscript and does practically nothing. I’m currently working on the installer script and I’ll consider adding a pull option.

[black7375]

#17 (comment)

I also update with git pull, and people who have used git often are probably doing that.
This is why I keep the current file structure.

By the time the 2.0 version comes out, there will be 3 installation guides.

• Manual Install: current guide
• Release Install: using the official release
• Install for Developers: using git clone & git pull

[ghost]

@black7375 I think the install.sh could cover the manual and release installation methods. Most people just want to get a UI fix, not a painstaking handcopy installation That could crαp itself when improperly copied.

[black7375]

Yes, that's right.

[travisnewman]

This all sounds great, thanks! :)

[ghost]

partially included in #93

[black7375]

I think it has been solved through v5.0.0's script.

• If there are any changes: Run git stash and git stash pop before and after git pull.
• If there are user-overrides.js, userChrome-overrides.css, and userContent-overrides.css files, proceed with override

[bb010g]

I use symbolic links to a repository checkout, and the new v5 layout would be even smoother if the new css directory containing leptonChrome.css and leptonContent.css was named leptonCss or similar, so as to not conflict with any other CSS subdirectories in $FIREFOX_PROFILE/chrome/.