summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorGravatar Chris Xiong <chirs241097@gmail.com> 2021-10-14 19:01:18 -0400
committerGravatar Chris Xiong <chirs241097@gmail.com> 2021-10-14 19:01:18 -0400
commit846cdbdbf965fc50478bcc4c6436e3dc6a489f3f (patch)
tree4a39385c982291a110f513871aba340f0a7a061e /README
downloadppo-846cdbdbf965fc50478bcc4c6436e3dc6a489f3f.tar.xz
Initial commit.
Diffstat (limited to 'README')
-rw-r--r--README22
1 files changed, 22 insertions, 0 deletions
diff --git a/README b/README
new file mode 100644
index 0000000..5398ccf
--- /dev/null
+++ b/README
@@ -0,0 +1,22 @@
+Chris' Private Gentoo Portage Overlay
+
+A lot of these ebuild files are just stolen from other overlays. As a principle
+I do not add third-party overlays to my system. Ebuilds are just shell scripts
+and despite being sandboxed malicious ones may still do unexpected harm to the
+system. Here is where I review third-party ebuilds and add them to my system.
+Occasionally I also add updated versions or fixes if some official ebuilds
+become unmaintained. All ebuilds here are only guaranteed to work with my
+particular setup. I don't test them for the sake of testing, i.e. This overlay
+is for private usage only. Use at your own peril.
+
+Chromium ebuilds until fairly recently (Chromium 87 I believe) were maintained
+by me. Those contain the VAAPI patch from Debian and are verified to be working
+on Intel iGPU. I stopped working actively on them since a) Chromium VAAPI works
+(almost) out of box on Linux desktop now and b) Stephan Hartmann
+(sultan@gentoo.org) stepped in and started doing God's work. You will probably
+never feel the pain to fix those stupid build errors with libstdc++ on an
+outdated dual core ULV processor... Current Chromium ebuilds are just forks of
+those in the official portage tree with minor tweaks. AND YOU SHOULD NOT USE MY
+OLD CHROMIUM EBUILDS BECAUSE NOBODY SHOULD USE AN OUTDATED BROWSER. They will be
+removed shortly.
+