Looking at the dpb manpage I noticed that under DPB_PROPERTIES it
mentioned tag:kde3 and tag:kde4. kde3/4 are long dead in the ports
tree so I see no need to mention them in DPB_PROPERTIES.

I've also pulled their mention from the "Still tainted" diagnostic
section.

ok?

--Kurt

Index: dpb.1
===================================================================
RCS file: /cvs/src/share/man/man1/dpb.1,v
diff -u -p -r1.36 dpb.1
--- dpb.1	10 Feb 2026 12:19:54 -0000	1.36
+++ dpb.1	8 Apr 2026 19:41:56 -0000
@@ -804,7 +804,6 @@ a progress percentage.
 .Pp
 This is followed by a host line, containing the name
 of each host used by dpb.
-Host names may be tagged with kde3 or kde4.
 They are followed by a
 .Sq `-'
 for unresponsive hosts, and the pid of the ssh master
@@ -915,16 +914,6 @@ and several build slots.
 Very large port that should be built in parallel, uses
 .Ev MAKE_JOBS
 and lots of build slots.
-.It Ar tag:kde3
-kde3 port that conflicts with kde4 ports.
-Prevent scheduling ports with
-.Ar tag:kde4
-on the same host.
-.It Ar tag:kde4
-kde4 port that conflicts with kde3 ports.
-Prevent scheduling ports with
-.Ar tag:kde3
-on the same host.
 .El
 .Sh THE SECURITY MODEL OF DPB
 When
@@ -1659,8 +1648,7 @@ will delay that.
 .Nm
 still keeps track of attempted junks.
 .It Still tainted: <bool>
-A host may have a tag (kde3/kde4) that prevents building differently tagged
-ports.
+A host may have a tag that prevents building differently tagged ports.
 This will be cleansed by
 .Ar junk
 eventually.