Date: Wed, 22 Nov 2023 13:41:43 +0800 From: Philip Paeps <philip@freebsd.org> To: Robert Clausecker <fuz@freebsd.org> Cc: Warner Losh <imp@bsdimp.com>, freebsd-arch@freebsd.org Subject: Re: Time to remove sccs tags Message-ID: <1CA7956B-8204-4328-A977-C874A3FAE0A7@freebsd.org> In-Reply-To: <ZV2P164Qhq8r7gK3@fuz.su> References: <CANCZdfo5Pj=AWmd5ftZ6OmMXBrkFAbZnYZt8EC8EqRqoi9csHw@mail.gmail.com> <22458D4C-35ED-4040-AAA1-A43006C0B32F@freebsd.org> <ZV2P164Qhq8r7gK3@fuz.su>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2023-11-22 13:21:27 (+0800), Robert Clausecker wrote: > Am Wed, Nov 22, 2023 at 01:15:14PM +0800 schrieb Philip Paeps: >> On 2023-11-22 00:12:48 (+0800), Warner Losh wrote: >>> It's been 30 odd years since the last csrg release. They are no >>> more. >>> >>> At this point I think we can safely remove the few sccs tags that >>> remain >>> in >>> the tree. The data will be there in git if we ever need it. >>> >>> Comments? >> >> Long overdue. >> >> Since we're removing all these tags, should we also remove what(1) >> and >> possibly ident(1) from the tree? >> >> Removing what(1) should be non-controversial at this stage. I can >> imagine >> some people may still be using ident(1) on extant Subversion systems. > > what(1) is part of POSIX, though I guess you can just install > devel/sccs > if you need it. I think the only reason we still have what(1) is because it was once useful to (help) identify the provenance of a file. It wasn't very good at it in the past, and it certainly isn't very good at it now. In 2002, Juli tried to resurrect SCCS for POSIX/SUS compliance. It looks like the attempt was aborted before FreeBSD 5.0-RELEASE though... Anyone who needs to tick this box in their standards compliance paperwork should simply install devel/sccs. :) Philip -- Philip Paeps Senior Reality Engineer Alternative Enterprises
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1CA7956B-8204-4328-A977-C874A3FAE0A7>