stackrpms - Rpm and dpkg build recipes for my custom packages

	Commit message (Collapse)	Author	Age
*	add some browser prefs	B Stack	2019-12-21
\| \| \| \| \|	fix #11 by adding some prefs to the packaged prefs.js for waterfox and palemoon. Some are specifically in case I used these as a reference for Firefox.
*	fix waterfox dpkg name	B Stack	2019-12-19
\|
*	waterfox 2019.12-classic builds on devuan!	B Stack	2019-12-19
\|
*	waterfox 56.2.14 dpkg	B Stack	2019-09-10
\|
*	waterfox 56.2.13 dpkg rc1	B Stack	2019-08-21
\|
*	add override_dh_strip_nondeterminism to waterfox	B Stack	2019-08-04
\|
*	waterfox 56.2.12 dpkg rc1	B Stack	2019-07-11
\|
*	freefilesync dpkg add unzip	B Stack	2019-07-11
\|
*	disable install-dir for wf	B Stack	2019-07-01
\|
*	waterfox 56.2.11 dpkg rc2 for obs	B Stack	2019-07-01
\|
*	waterfox 56.2.11 dpkg rc1	B Stack	2019-06-28
\| \| \| \| \| \| \|	I used waterfox commit 63b480e to build, and possible due to that, I had to disable patch waterfox-install-dir, which is not reflected in this commit, in case the install dir is adjusted for the upstream release tarballs.
*	waterfox remove unity patch which was upstreamed	B Stack	2019-06-13
\|
*	waterfox 56.2.10.1 rpm and dpkg rc1	B Stack	2019-06-13
\|
*	palemoon 28.5.1 rpm rc1	B Stack	2019-06-04
\|
*	waterfox 56.210 dpkg	B Stack	2019-05-23
\|
*	waterfox dpkg: actually use bgstack15 prefs js	B Stack	2019-05-19
\| \| \| \| \| \|	It came to my attention that waterfox dpkg was not actually deploying my prefs javascript file. It was simply not placed in the dpkg file!
*	waterfox 56.2.8-1+devuan dpkg ready	B Stack	2019-03-29
\| \| \| \|	Imported some build-depends from hawkeye116477
*	WIP: waterfox dpkg	B Stack	2019-03-29
\|
*	waterfox use stack prefs in rpm	B Stack	2019-03-09
\|
*	waterfox dpkg rc1	B Stack	2019-03-08
\|
*	WIP: initial bgstackification	B Stack	2019-03-07
\|
*	WIP: waterfox dpkg	B Stack	2019-03-06