Page MenuHomeFreeBSD

[phb]: Document inclusion of Makefile.* files
ClosedPublic

Authored by fernape on Aug 29 2023, 6:57 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Apr 23, 12:43 AM
Unknown Object (File)
Jan 27 2024, 9:02 AM
Unknown Object (File)
Jan 10 2024, 8:01 AM
Unknown Object (File)
Dec 30 2023, 3:11 AM
Unknown Object (File)
Dec 20 2023, 8:35 AM
Unknown Object (File)
Dec 14 2023, 10:55 AM
Unknown Object (File)
Nov 21 2023, 11:27 PM
Unknown Object (File)
Oct 15 2023, 4:52 AM
Subscribers

Details

Summary

Document the automatic inclusion of several Makefile.* files.
Also mention idiomatic splitting of pkg-plist.* files.

PR: 244742
Reported by: salvadore@

Test Plan
  • Apply patch
  • make documentation

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

fernape created this revision.

Ok but use the one sentence per line please, no need to update the review, can be changed in the commit.
Apart from that ok from docs side :)

This revision is now accepted and ready to land.Aug 29 2023, 7:00 AM

Ok but use the one sentence per line please, no need to update the review, can be changed in the commit.
Apart from that ok from docs side :)

Ummm.. I think I did. Did I miss one?
Maybe the confusion is that the lines are wrapped at 80 characters?

documentation/content/en/books/porters-handbook/special/_index.adoc
57

This line for example, maybe you have something configured in your editor.

Ok but use the one sentence per line please, no need to update the review, can be changed in the commit.
Apart from that ok from docs side :)

There is a fair bit that needs to be corrected in here.
Please hold off and I’ll send feedback this evening.

documentation/content/en/books/porters-handbook/special/_index.adoc
57

Yes, that's wrapping.

From https://sembr.org/

"A maximum line length of 80 characters is RECOMMENDED"

I always understood semantic breaking as "don't put two or more sentences in one line", not as "you should never break a single sentence in multiple lines" :-)

documentation/content/en/books/porters-handbook/special/_index.adoc
55

"Sometimes, port Makefiles can be really long"

56

"example", over instance

59

In cases like this, it can be convenient

64

s/in case/if/

70

typo of example

74

s/idiomatic/usual practice/

s/the port in several/the port into several/

74–75

"if" rather than "in case"

80–81

Not sure what this means - do you mean "the framework does not split the packaging list into multiple files automatically, as the logic involved may be complex"?

This revision now requires review to proceed.Aug 29 2023, 5:19 PM
fernape added inline comments.
documentation/content/en/books/porters-handbook/special/_index.adoc
80–81

Yes, it wasn't clear.

Is it better now? It is just to mark the difference. The recognized Makefile.* files are included automagically. pkg-plist.* need to handled manually.
Something like

.if ${ARCH} == i386 
PLIST=pkg-plist.i386
...
grahamperrin added a subscriber: grahamperrin.

One sentence per line. Thanks.

This revision now requires changes to proceed.Aug 31 2023, 2:03 AM
fernape marked an inline comment as done.
  • One sentence per line
documentation/content/en/books/porters-handbook/special/_index.adoc
55
56
57
58

… alternatively,

In such cases, …

70
70

Selected where?

73

The preceding sentence described it as a file. No need to repeat the description for the same filename.

One sentence per line. Thanks.

documentation/content/en/books/porters-handbook/special/_index.adoc
70

What do you mean?

documentation/content/en/books/porters-handbook/special/_index.adoc
70

I mean, maybe /selected/ is not the ideal word.

ceri added inline comments.
documentation/content/en/books/porters-handbook/special/_index.adoc
80–81

Much clearer, thanks!

documentation/content/en/books/porters-handbook/special/_index.adoc
70

I don't know what other word to use, to be honest.
For flavored ports, you select a flavor. "Choose" might be an option, but I prefer the former.

This revision was not accepted when it landed; it landed in state Needs Review.Sep 1 2023, 7:57 AM
This revision was automatically updated to reflect the committed changes.

Thank you all for the review.

@grahamperrin if you find a more suitable word to replace "select", please let me know.