Page MenuHomeFreeBSD

[special] igor -Ry and some other rewording and fixes.
ClosedPublic

Authored by mat on Aug 20 2014, 3:08 PM.

Diff Detail

Repository
rD FreeBSD doc repository - subversion
Lint
No Linters Available
Unit
No Unit Test Coverage

Event Timeline

mat retitled this revision from to [special] igor -Ry and some other rewording and fixes..
mat updated this object.
mat edited the test plan for this revision. (Show Details)
wblock added inline comments.
en_US.ISO8859-1/books/porters-handbook/special/chapter.xml
13–14

<para>This section explains the most common things to consider when creating a port.</para>

45

s/mostly/mostly be/

70

This one actually needs "should". It's a recommendation on when to create directories.

75

s/has to be/is/

223

s/upstream/the upstream/

251

setting <varname>USE_LDCONFIG</varname> to a list of

253

s/example/example,/

255

<filename>PREFIX/lib/bar</filename>,

321–322

s/has to/must/

324

s/in to/into/

327

s/cannot not be/cannot be/

377

<varname>RESTRICTED</varname>, since the latter variable

502

s/else/other/

504

s/Same/The same/

668

s/if port/if the port/

883

s/^/an /

949

Break sentence at NLS. Also use <acronym> tags on NLS.

957

s/on//

1006

may be needed, such as

1006–1007

In high complexity cases, more advanced techniques

1060

s/like/as/

1336

I think this is one where "should" is correct.

2044

s/so that/for/

2075

When set, add the selected JDK port to the build dependencies.

2083

When set, add the selected JDK port to the run dependencies.

2090

When set, add the selected JDK port to the extract dependencies.

2114

Should this have the single quotes?

2259

"forecited" is a word, but a rare one. "previously listed variables" is better.

2285

s/is/are/

2341

s/use/uses/

2374

s/must/is/

2374–2375

s/the//

2575

mygroup</literal> if the port needs different values. This

2576

allows the user to override them easily.</para>

2580

s/the/a/

2719

s/must make sure to/must/

2970

Do not redefine these variables in the port.

3161

s/entries using/entries for/

3592

s/default define/default, define/

3601–3602

s/version define/version, define/

4365

This is a recommendation:

earlier, all ports scripts should use</para>

4409

s/have/have a/

4410

s/If so that/If so, that/

4493

"Should" is a recommendation here, and correct.

en_US.ISO8859-1/books/porters-handbook/special/chapter.xml
1336

I don't think so, if it has those files, they must be listed in the plist, and be installed in the directory below. Maybe i should have used "must" and not "have to" ?

2075

Should I add <acronym> around JDK too ? should I do this everywhere ?

2114

nope.

Update with comments from wblock

en_US.ISO8859-1/books/porters-handbook/special/chapter.xml
1336

Yes, "must" is more definite than "have to".

2075

Yes. Anything that is an acronym should have <acronym> tags.

wblock added a reviewer: wblock.

Please build-test, then commit.

This revision is now accepted and ready to land.Sep 15 2014, 9:39 PM
mat updated this revision to Diff 1638.

Closed by commit rD45616 (authored by @mat).