notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Want a good monitor light? See my photosAll times are UTC
Ukraine
This referral link gives you 10% off a Fastmail.com account and gives me a discount on my Fastmail account.

Get notified when packages are built

A new feature has been added. FreshPorts already tracks package built by the FreeBSD project. This information is displayed on each port page. You can now get an email when FreshPorts notices a new package is available for something on one of your watch lists. However, you must opt into that. Click on Report Subscriptions on the right, and New Package Notification box, and click on Update.

Finally, under Watch Lists, click on ABI Package Subscriptions to select your ABI (e.g. FreeBSD:14:amd64) & package set (latest/quarterly) combination for a given watch list. This is what FreshPorts will look for.

non port: devel/include-what-you-use/pkg-descr

Number of commits found: 3

Wednesday, 7 Sep 2022
21:58 Stefan Eßer (se) search for other commits by this committer
Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)
commit hash: fb16dfecae4a6efac9f3a78e0b759fb7a3c53de4 commit hash: fb16dfecae4a6efac9f3a78e0b759fb7a3c53de4 commit hash: fb16dfecae4a6efac9f3a78e0b759fb7a3c53de4 commit hash: fb16dfecae4a6efac9f3a78e0b759fb7a3c53de4 fb16dfe
Tuesday, 23 Apr 2019
05:29 koobs search for other commits by this committer
devel/include-what-you-use: Update to 0.11

PR:		234429
Submitted by:	Greg V <greg unrelenting.technology>
Original commitRevision:499716 
Sunday, 21 Feb 2016
15:05 koobs search for other commits by this committer
[NEW] devel/include-what-you-use: Clang tool to analyze #includes in C and C++
sources

"Include what you use" means this: for every symbol (type, function,
variable, or macro) that you use in foo.cc (or foo.cpp), either foo.cc
or foo.h should include a .h file that exports the declaration of that
symbol. (Similarly, for foo_test.cc, either foo_test.cc or foo.h should
do the including.) Obviously symbols defined in foo.cc itself are
excluded from this requirement.

This puts us in a state where every file includes the headers it needs
to declare the symbols that it uses. When every file includes what it
uses, then it is possible to edit any file and remove unused headers,
without fear of accidentally breaking the upwards dependencies of
that file. It also becomes easy to automatically track and update
dependencies in the source code.

WWW: http://include-what-you-use.org
Original commitRevision:409295 

Number of commits found: 3