Change the description of the 'tag' property to something more generic:
- There are no more ports that have DPB_PROPERTIES=tag:{kde3,kde4} set
in their Makefile;
- Explain that only one tag set can be used.
The 'tag' property comes in handy to solve a dpb build issue with the
two audacious flavors. Instead of using a port specific tag name use
generic a/b.
Does this make sense?
Index: dpb.1
===================================================================
RCS file: /cvs/src/share/man/man1/dpb.1,v
retrieving revision 1.20
diff -u -p -r1.20 dpb.1
--- dpb.1 4 Apr 2020 08:41:54 -0000 1.20
+++ dpb.1 27 Feb 2021 07:49:13 -0000
@@ -872,16 +872,19 @@ 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.
+.It Ar tag:a
Prevent scheduling ports with
-.Ar tag:kde4
+.Ar tag:b
on the same host.
-.It Ar tag:kde4
-kde4 port that conflicts with kde3 ports.
+.It Ar tag:b
Prevent scheduling ports with
-.Ar tag:kde3
+.Ar tag:a
on the same host.
+.El
+.Pp
+Note that multiple
+.Ar tag
+sets will not work simultaneously, thus only one set can be used.
.El
.Sh THE SECURITY MODEL OF DPB
When
