third_party/polymer/README.chromium - Issue 920223002: Replace CRLFs in Polymer source files with LFs.

Side by Side Diff: third_party/polymer/README.chromium

Issue 920223002: Replace CRLFs in Polymer source files with LFs. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Update reproduce.sh with literal '\r' Created 5 years, 10 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

« no previous file with comments | « no previous file | third_party/polymer/reproduce.sh » ('j') | no next file with comments »

OLD	NEW
1 Name: Polymer	1 Name: Polymer

2 Short Name: polymer	2 Short Name: polymer

3 URL: http://www.polymer-project.org	3 URL: http://www.polymer-project.org

4 Version: 0.5.2-4	4 Version: 0.5.2-4

5 Revision: (See components/<component>/.bower.json)	5 Revision: (See components/<component>/.bower.json)

6 License: BSD	6 License: BSD

7 License File: LICENSE.polymer	7 License File: LICENSE.polymer

8 Security Critical: no	8 Security Critical: no

9	9

10 Description:	10 Description:

(...skipping 20 matching lines...) Expand all Loading...
31 2. A next-generation web application framework built upon these core	31 2. A next-generation web application framework built upon these core

32 technologies called the Polymer.	32 technologies called the Polymer.

33	33

34 Local Modifications:	34 Local Modifications:

35 - Removed executable bit from the files in 'components/core-list'.	35 - Removed executable bit from the files in 'components/core-list'.

36 - Created a copy 'components-chromium' of the 'components' directory with the	36 - Created a copy 'components-chromium' of the 'components' directory with the

37 only difference that all inline JavaScript blocks are extracted from Polymer	37 only difference that all inline JavaScript blocks are extracted from Polymer

38 HTML elements to external JS files. This version of the Polymer is used in a web	38 HTML elements to external JS files. This version of the Polymer is used in a web

39 UI, where CSP forbids an execution of inline scripts. The extraction was made	39 UI, where CSP forbids an execution of inline scripts. The extraction was made

40 with the help of the Vulcanize tool (https://github.com/Polymer/vulcanize).	40 with the help of the Vulcanize tool (https://github.com/Polymer/vulcanize).

41 - Stripped whitespace using sed (this or a similar command will be added to	41 - Replaced CRLF line endings with LF line endings in text files.

42 reproduce.sh shortly, but for now is done manually - see crbug.com/458315):

43 find components components-chromium -type f \( -name \.html -o -name \.css -o -name \.js -o -name \.md -o -name \.sh -o -name \.json -o -name \*.gitig nore \) -print0 \| xargs -0 sed -i 's/\r$//g'

44

45	42

46 To restore a content of the 'components', 'components-chromium' directorires	43 To restore a content of the 'components', 'components-chromium' directorires

47 from scratch, run ./reproduce.sh (requires bower and vulcanize >= 0.7.2).	44 from scratch, run ./reproduce.sh (requires bower and vulcanize >= 0.7.2).

48	45

49 Note on Bower:	46 Note on Bower:

50 The directory can be updated by running "bower update". A new component can be	47 The directory can be updated by running "bower update". A new component can be

51 installed by running "bower install -S Polymer/<component>#version". Be sure to	48 installed by running "bower install -S Polymer/<component>#version". Be sure to

52 add the .bower.json file to the repository as it includes the revision	49 add the .bower.json file to the repository as it includes the revision

53 information of the polymer component.	50 information of the polymer component.

54 Also be sure that you listed all the added packages and **all their	51 Also be sure that you listed all the added packages and **all their

55 dependencies in bower.json, and specified exact** versions of every package	52 dependencies in bower.json, and specified exact** versions of every package

56 explicitly. That is needed because Bower can't handle recursive dependencies	53 explicitly. That is needed because Bower can't handle recursive dependencies

57 correctly (see http://stackoverflow.com/q/25899532).	54 correctly (see http://stackoverflow.com/q/25899532).

OLD	NEW