Search results

We are all in violent agreement, here.

My experience is that ports with one maintainer are dealt with much more quickly than ports maintained by a mailing list. Also, various scripts in the ports tree assume that there is only one value in the MAINTAINER field, as does FreshPorts and at least one other codebase I could name. I have...

This has been going on in the FreeBSD Discord for a while. At the moment, it has hit a lull.

Putting additional requirements on existing volunteers won't work. As often as not, they will simply walk away. Even if they don't, they are on a path to burnout. We do need more volunteers, especially to review and commit more patches.

To be auto-assigned, Bugzilla PRs need to start with "<category>/<portname>". Then Bugzilla sends email and perhaps changes the assignee (if they are @FreeBSD.org). If anyone sees ones that aren't, just email bugmeister@FreeBSD.org, and we will manually fix them. PRs come in so fast that it...

I would instead email the maintainers directly. OTOH it seems like someone from at least ports-secteam@ has replied on the 28th.

Yes, and Devin has been overwhelmed as a result of Real Life (TM), and is likely to be scarce for a while.

Also in terms of Bugzilla PRs, traditionally things affecting only laptop/desktop users have been assigned to "multimedia@FreeBSD.org". OTOH this is one of our mailing lists that is mostly inactive except for having PRs assigned to it. But it can still be useful for browsing PRs...

So fwiw I (as wiki-admin) made some minor changes to the wiki article (nothing substantial, just to make it more FreeBSD-wiki-flavored). But what I found while I was messing around there is that there were N laptops missing from CategoryLaptop. I have now fixed that...

Ding! In general "those software projects" are also maintained by volunteers. So, which set of volunteers do you think should do the work? Upstream? The OSes?

Perhaps because we ask too much of them? (3 major branches times N architectures?)

Warner Losh (imp@) was the driving force behind the idea of FCPs, as a potential way to move "calls for comment" off the mailing lists and into something more formal/more visible. Uptake was not what I personally would have hoped. You'd have to ask imp for his intentions going forwards.

I also loathe the overriding of LLVM_DEFAULT and fight it wherever I find it. IMHO this should be user-settable and not overridden internal to a port. Let me guess: graphics/mesa-dri, right?

And now for some experimentation to see what happens using only the libraries in base. In general, these dependencies are introduced only in places where the base system libraries are _known_ not to satisfy the requirements. This is particularly true if you look at some of the graphics ports...

Yes, it broke during a recent "minor" port upgrade. I am looking into it. fwiw, I don't generally monitor the forums, so either Bugzilla or email are the best ways to reach me. Thanks.