Page MenuHomeFreeBSD

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

Authored by mat on Aug 20 2014, 3:06 PM.
Tags
None
Referenced Files
Unknown Object (File)
Feb 20 2024, 8:22 PM
Unknown Object (File)
Dec 19 2023, 6:39 PM
Unknown Object (File)
Dec 16 2023, 9:10 PM
Unknown Object (File)
Nov 8 2023, 11:04 AM
Unknown Object (File)
Nov 6 2023, 7:44 PM
Unknown Object (File)
Nov 6 2023, 7:26 PM
Unknown Object (File)
Nov 6 2023, 12:01 AM
Unknown Object (File)
Nov 5 2023, 12:24 PM
Subscribers

Diff Detail

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

Event Timeline

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

the strings?

wblock added inline comments.
en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml
533–534

It's a little ambiguous. Maybe "any of these strings".

Also, s/note/not/

534

"should be" is okay here, it is making a recommendation. But this sentence is vague. It's hard to tell what it is saying. The string should be different... from what? I think it is saying that the wording of the message depends on which variable is used. The example shows that BROKEN and IGNORE are worded differently.

Rewords a bit after antoine and wblock's comments

en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml
38–40

The <filename>pkg-<replaceable>*</replaceable></filename> files can be modified by <link linkend="pkg-names">redefining a variable</link> rather than overwriting the file.

67

Some code needs modifications or

189

The rest of the sentence starting with "and" seems unnecessary here.

Also, if we must include smileys, they should probably be &#x263A;.

217

s/resaonnable/reasonable/

218

s/,//

281

Break sentence at semicolon.

308

s/System/The system/

344

Do send applicable changes and patches to the upstream

345

maintainer for inclusion in the next release of the code.

346

This makes the next release that much easier.

377–378

s/cases/cases,/

378

There are several variables that can be used in a port's <filename>Makefile</filename> to tell the user that the port cannot be installed.

381

<command>make</command> is not really needed here.

382

s/given back/shown/

383

Remove <command>make</command>.

384

variable. Each variable conveys radically different

385

meanings, both to users and to automated systems that depend on

386

"the" is not needed here.

521

"it will be checked" is ambiguous.

If this variable is set, <filename>/usr/lib32</filename> must be present for IA32 versions of libraries and the kernel must support IA32 compatibility.

535

Due to the way the information is shown to the user, the wording of messages for each variable differ:</para>

634

s/Check/Verify/

647

s/Maybe also contact/Contact/

655

Break sentence after "information".

658

The quotes seem unnecessary.

to get the executable name.

660

s/behaviour/behavior/

706

Break sentence after "way".

en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml
217

Spelling: s/reasonnable/reasonable/

mat updated this revision to Diff 1641.

Closed by commit rD45618 (authored by @mat).