Update gprbuild-bootstrap Makefile

Works here on a custom host at -CURRENT.

I was thinking of rcorder(8) for kernel. Of course run at compilation time, not an startup.

I'm not taking this task :) I just want to make kernel -Werror-assing-enum clean.

In D56898#1322713, @des wrote:

Well for starters, you should not be deleting etc/mtree/BSD.root.dist.

In D55552#1320153, @thierry wrote:

Yes, very good idea!
Is this alias ready?

Why not use ada@FreeBSD.org.? philip@freebsd.org (postmaster@) is working on setting this mailing list up. The idea of using ada@ for Ada Ports was suggested by Marcin (saper@) in[[ https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277852 | PR 277852 ]]. The mailing list would function as a place to discuss changes such as this, as well as architecture design solutions with completing the integration of Ada within FreeBSD, breaking the monolithic gnat packages into *-bootstrap, *-libs(or runtime), adding the LLVM Ada toolchain, expanding the Ada USES framework, including gprbuild/install, a place for users, and much more.

This is a much need QOL improvement for integrating Ada libraries into the Ports Tree. I have been using this diff while working on adding some Ada ports, thanks for the work.

What else needs work here?

Man page was checked with mandoc -T lint, igor, and aspell check --lang=en --mode=nroff as per the Documentation Project Primer for New Contributors, the only issue was a lack of SYNPOSIS

sysctl.conf(5): Add support for sysctl.conf.d

Another solution, move /etc/sysctl.conf.d to EXAMPLES, and provide two or three examples there?

In D56898#1303487, @antranigv_freebsd.am wrote:

👍 +1! I Approve! Thank you! directorize all the things!

Correct typo in sbin/sysctl/sysctl.conf:
"to through to" becomes "through to"

• Update stock sysctl.conf
• Update man page date

In D56898#1303540, @ziaee wrote:

Please add Relnotes: yes to the commit message.

In D56898#1303540, @ziaee wrote:

Please add Relnotes: yes to the commit message.

In D56898#1303538, @des wrote:

Should we add a comment to the stock sysctl.conf?

Uploaded git-arc patch.

Should the directory be tagged as rc, similar to https://reviews.freebsd.org/D56900?

Sure I will give it a shot. Is this because my git formatted-patch was striped of the preamble?

There is an updated review at https://reviews.freebsd.org/D56898, based on Antranig's patch.

I am not sure on the sorting in the man page.

Updated diff with D${num}

Fucking hell, two platforms for the same thing is a waste of time: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286225

Committed:
https://cgit.freebsd.org/ports/commit/?id=fb9a10d1c7cfc0dcfbe3c3adf3b0dbd53de5168d

Suggestions poudriere-testport devel/py-setuptools:
main-amd64-default: Pass
main-i386-default: Pass
13_4-amd64-release: Pass
13_4-i386-release: Pass
14_1-amd64-release: Pass
14_1-i386-release: Pass
14_2-amd64-release: Pass
14_2-i386-release: Pass

main-i386-default eventually passed.

I have updated my patch, and created a new PR at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284845

extproc/py-sphinxcontrib-applehelp was updated to 2.0.0 in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283871

Oh shit, I missed this when adding https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284844

https://cgit.freebsd.org/ports/commit/?id=ed915b6d812b4193a196a70603d8967342d918ee

Hello, is it possible to build on the work in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268018? The patch there is dated, but it includes the optional WEBSUPPORT, and cleanups from the various port tools.

Another patch has been committed:
https://cgit.freebsd.org/ports/tree/www/newsraft

Has portlint, or similar, been run?

Update to 0.23.

poudriere-testport:
13.3-{amd64,i386}-release: OK
14.0-{amd64,i386}-release: OK
main-{amd64,i386}: OK

In D43478#991623, @arrowd wrote:

I pushed this version of pyinstaller-hooks-contrib into the main tree. Christopher, if you think anything should be done differently please provide a patch and I will push it ASAP.

Thanks Alastair for picking this up and sorry Christopher for this taking so long to push.

• Drop py-pip, it is not needed
• Improve DOC components

• Improve DOCS
• Include building the man page.

Add tests component

Fix Port tests component

Move pytest from ${USES} to ${USE_PYTHON}

Move pytest from ${USES} to ${USE_PYTHON}

Move pytest from ${USES} to ${USE_PYTHON} for real this time.

Move pytest from ${USES} to ${USE_PYTHON}

• Update ${TEST_DEPENDS} with https://reviews.freebsd.org/D43484
• Add NO_ARCH as per poudriere-testport's recommendation

Hello Christopher, thanks for the work, made updating your patch easy,
https://reviews.freebsd.org/D43478

There are one too many places for existing bugs, apologies for not checking this platform for an update to py-pysintaller-6.3.0. As a result of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275494#c38, I started to work on some Ports, py-pyinstaller being the first. I am not too confident on the work I have done, and would appreciate a review.

In D43253#990385, @diizzy wrote:

Poudriere reports:

Error: mail/py-flask-mailman depends on nonexistent origin 'textproc/py-mkdocs-include-markdown-plugin'; Please contact maintainer of the port to fix this.

Update to 5.0.23

Update to 5.0.32

In D43253#985836, @minsoochoo0122_proton.me wrote:

In D43253#985801, @agh_riseup.net wrote:

In D43253#985787, @minsoochoo0122_proton.me wrote:

Please add ports group to reviewers, subscribers, and tag otherwise people won't be notified.

I have no idea what that entails. If I Edit Revision via the menu box at the top right, I can find the three fields you mention, however, when I type ports, a number of options are auto populated in a drop down list, none of which are ports.
Is this meant to be standard procedure too?

Try Contributor Reviewers (ports)

In D43253#985787, @minsoochoo0122_proton.me wrote:

Please add ports group to reviewers, subscribers, and tag otherwise people won't be notified.

In D42185#968867, @diizzy wrote:

That made things a lot clearer, I was a bit concerned that it would "pollute" /usr being described as a package manager. While there are no restrictions on packaged applications in terms of operation (excluding harmful software etc) it's good if we can keep installed files from packages unaltered and not trying to "work around" the ports framework whenever possible.

• Update to 2.0.0
• Cleanup files/pkg-message.in

In D42185#965792, @diizzy wrote:

Can you elaborate a bit on why this is needed as it seemingly will interfere with our own package framework?

All suggestions should be addressed in the updated diff.
Thanks for the review.

Updated diff in response to dizzy's feedback:

Thanks for the feedback.

devel/csfml: Address items in review D41519