cvs commit: ports/security/portaudit-db/database portaudit.txt
portaudit.xlist portaudit.xml
Jacques A. Vidrine
nectar at FreeBSD.org
Tue Aug 17 11:27:30 PDT 2004
On Tue, Aug 17, 2004 at 08:26:56PM +0200, Oliver Eikemeier wrote:
> epoch 0? 1970-01-01? Or the date vuxml was announced? This would be
> easier to find than XXX, especially in a rendered version. Or just leave
> the entry empty.
>
> Any constant will do, it could be easily rendered to `unknown'. I find a
> non-constant value (date of entry) a bad choice it is more difficult to
> test against (and could be correct).
Yes, you are right, we just need a constant string like 'unknown' or
'unspecified'.
> >By way of example, I've been using FreeBSD 4.7-RELEASE-p1 == 4.7_1. I'm
> >not entirely satisfied and I am open to suggestions. This part has been
> >ill-specified. :-(
>
> Ehm, __FreeBSD_version? What's bad with that? Documented in the Porters
> Handbook, and to find out.
__FreeBSD_version is for developers, not users. Users need to see
actual release numbers.
Cheers,
--
Jacques Vidrine / nectar at celabo.org / jvidrine at verio.net / nectar at freebsd.org
More information about the freebsd-vuxml
mailing list