Date: Thu, 20 Nov 2014 18:13:58 -0500 From: Shawn Webb <lattera@gmail.com> To: =?iso-8859-1?Q?Ren=E9_Ladan?= <rene@freebsd.org> Cc: chromium-list freebsd <freebsd-chromium@freebsd.org> Subject: Re: backing down on Chromium ... Message-ID: <8A50107E-55F9-4AD1-981A-5A52DDB5DC0A@gmail.com> In-Reply-To: <546E72B9.60700@freebsd.org> References: <546E72B9.60700@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_7E422C50-6C7C-426A-8C1F-51E00C0DA013 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Nov 20, 2014, at 6:01 PM, Ren=E9 Ladan <rene@freebsd.org> wrote: > Signed PGP part > Hello all, >=20 > after already four years I decided to back down somewhat on Chromium. > This is not an overnight decision, the feeling started creeping in > several months ago. >=20 > One reason is that maintaining Chromium all the way on FreeBSD would > seriously be a good candidate for a full-time job: > - keep the existing patches working, they need to be checked and > possibly rewritten on every major release > - polishing patches for upstream and tickling the upstream bots > - hunting down incompatibilities. This is mostly caused FreeBSD > masquerading as Linux and consequently Chromium assumes that e.g. > /proc is populated as on Linux. > - writing missing code for FreeBSD, including but not limited to: > - low-level network stuff > - fcvt(3) > - obtaining hard disk drive serial number for the Google Music (if > I understand correctly) > - obtaining detailed memory usage, proper GPU porting > - keeping the GitHub and ports version in sync > - writing VuXML entries once in a while > Also, other things seem more interesting (e.g. FreeBSD documentation = or > other ports), and sometimes I felt more like being a Chromium than a > FreeBSD developer. >=20 > This does mean that *you* will have to continue, but I (boldly) think > there is enough interest for it. This should hopefully get you = started: > - As you might know, we have an work-in-progress repository on GitHub: > https://github.com/gliaskos/freebsd-chromium/ > - Patches are available in the Ports Tree and on GitHub. There are = also > experimental patches against the top-of-tree (like FreeBSD-CURRENT) = at > https://people.freebsd.org/~rene/chromium/ > - The latter location also contains a script to generate the patches > (gen-diff.sh) and a script to try to build chromium in a chroot > (update.sh). It also contains a list of required packages = (pkg-list). > Note that libxml2 and yasm can go once the bundled versions work. > - Minor version updates are mostly a matter of running `make makesum` > and checking if the pkg-plist is still OK. See below for major > version updates. > - Notice that new upstream distribution files can take a day to = appear, > even in the case of a security update. >=20 > Porting a new major version (for GitHub or the Ports Tree) is a > different story though: > - Checkout the beta branch at GitHub > - Bump the PORTVERSION, run `make makesum` > - Run `make checkpatch` to see which patches still apply. Temporarily > move Broken / orphaned patches out of the way. Repeat till > `make checkpatch` is fine. > - Fix or delete the patches you just moved > - Try to build the port. Have coffee, brain, and willpower ready... > - If `make configure` fails, this is mostly because gyp is = complaining. > In case a directory got accidentally deleted by the > remove_bundled_libraries.py script, put it back in, add it to its > list, and try again. > - In case you need inspiration for a patch, try to look at the > corresponding Linux or MacOSX code. A lot of times adding BSD to = the > list suffices. > - Once Chromium links and staging passes, run `make check-plist` and > `make package` to see if the package list is still OK. > - Try to run it. > - Once that works, you can send the patches using a PR, a website, or > otherwise. > - Every six weeks or so the Beta version gets Stable, which means it = is > time to merge the beta branch back into the master branch. > - To get the patch for the Ports Tree, replace the old files/ = directory > with the new one, and update Makefile, pkg-*, and distinfo >=20 > In case you feel like working with upstream: > - See the WWW site for some hints on getting started > - Have a modern machine ready (many cores, RAM, ZFS, ccache) > - Check upstream on how to get the sources (chroot highly recommended > to not pollute your existing system). Notice that the initial > checkout can is between 10 GB and 15 GB large. > - Apply the patches from https://people.freebsd.org/~rene/chromium/ > - Run the script to try to build Chromium: > sh ./update.sh build nopull > Even more coffee, brain, and willpower recommended. > - To update from upstream, run: > sh ./update.sh > and check for merge conflicts in the git output. >=20 > Resources: > - https://googlechromereleases.blogspot.com/ > - chromium-dev@chromium.org > - chromium-packagers@chromium.org > - #chromium on FreeNode >=20 > For now I will continue to: > - Committing VuXML entries > - Committing new versions to the Ports Tree (e.g. as PR) and to = GitHub. > Feel free to fork the repository. > - Answer any questions you have. >=20 > Do mind that (at least in my experience), interest from upstream in = BSD > varies. There might eventually be BSD bots, but that doesn't > necessarily mean that build errors on BSD will be blocking (as they = are > on Windows / Linux / MacOSX / Android / iOS). >=20 > A good person to contact would be Pawel Hajdan Jr > <phajdan.jr@chromium.org> >=20 > Regards, > Ren=E9 Hey Ren=E9, As someone who uses Chromium on a daily basis (and admittedly takes it = for granted), I would like to give you a sincere thank you for your hard = work. I=92m hoping that the person who fills in your big, worn shoes = will achieve the same level of awesomeness. Good luck in your future endeavors. Thanks, Shawn --Apple-Mail=_7E422C50-6C7C-426A-8C1F-51E00C0DA013 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJUbnW5AAoJEGqEZY9SRW7u3psP/jveYy6n7Y1rwtZSBoR/+CnW HI6v7Gs2TEU/0NoxiqOPWz4khnhk0zxbuGFmad+SJY8tXic9JaYeJGDkhNFm+yEU YKbD6BGccM0uGxpUpl2Pb29sn/YI15qJHu1237WCq00FQRAuAfkY3S6CtSRtyvgX /i2DfFKdVOm62MBO8n+aeGnVYAaN1zVmlSwYjfY7Qn3V50iYYg+j/+zAo9erAqzT SYRqewIjS76P6vQPiytKUS10avrv9QjaXAWPPxCyLa8r292cMK963exAhC56Gjtc wIIFCL2esKpk3Z/aAZRVJFSL9meDZJQMI7dE1z4jz0WNgA9Wh0GCmWxlcKGe15EZ w1SfjNfxwZ6xxjuERZ04qzYdV+oB6IcgdiO7rnb+y55gCCn8nT0blZrnHi1rOtKA d4bsP5FQiTWu+/3ILa2rxuZ40HOFy7I7roh5R5Vqjt01Kg68uzzSH5K6JQM37L3r cssD03j19oNzBebR4Fny56Z++XTtYOVv1LxiEF+hc3HkWeRgIOi8+IXgPWJ28xb8 CU8ealyuVhw+6d8Xljj6Nnt6q7yNHuNfjQPS8yuPnjvEjOOevJDdgLtXhG12CH4+ X3z/a7kJ0kcnvlvoW5MioQ3kv0LybwbaPdrGgYjiW8PTLVV5VKTI94U9voVYKjNX SEZxu1cN94o4PgkVhM/d =1slt -----END PGP SIGNATURE----- --Apple-Mail=_7E422C50-6C7C-426A-8C1F-51E00C0DA013--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8A50107E-55F9-4AD1-981A-5A52DDB5DC0A>