build/linux/unbundle/README - Issue 13732002: Linux: move use_system_harfbuzz logic out of the main file.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: build/linux/unbundle/README

Issue 13732002: Linux: move use_system_harfbuzz logic out of the main file. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: README Created 7 years, 8 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

OLD	NEW
(Empty)
	1 This directory contains files that make it possible to use system libraries.

	2

	3 For more info please read the following:

	4

	5 - https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries

	6 - https://wiki.gentoo.org/wiki/Why_not_bundle_dependencies

	7 - http://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles

	8

	9 For more Chromium-specific context please read

	10 http://spot.livejournal.com/312320.html .

	11

	12 This directory is provided in the source tree to follow above guidelines.

	13 It is a compromise solution which takes into account Chromium developers

	14 who want to avoid the perceived burden of more conditional code in gyp,

	15 and expectations of Open Source community, where using system-provided

	16 libraries is the norm.
	darin (slow to review) 2013/04/22 19:11:33 This is a good description of "why" this code exis This is a good description of "why" this code exists, but it probably would be nice to include a "how" section, so it is clear how one might actually use this module. You might consider adding some sample command lines that show how to use the python script, etc.? Paweł Hajdan Jr. 2013/04/22 21:07:18 Good point. Done. Thanks! Show quoted text On 2013/04/22 19:11:33, darin wrote: > This is a good description of "why" this code exists, but it probably would be > nice to include a "how" section, so it is clear how one might actually use this > module. You might consider adding some sample command lines that show how to > use the python script, etc.? Good point. Done. Thanks!
OLD	NEW

« no previous file with comments | « no previous file | build/linux/unbundle/harfbuzz.gyp » ('j') | no next file with comments »