Date: Mon, 3 Feb 1997 03:26:53 +0000 (GMT) From: Adam David <adam@veda.is> To: jfieber@indiana.edu (John Fieber) Cc: chuckr@glue.umd.edu, CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-ports@freefall.freebsd.org Subject: Re: cvs commit: ports/www/sawt - Imported sources Message-ID: <199702030326.DAA28432@veda.is> In-Reply-To: <Pine.BSI.3.95.970202203402.17748F-100000@fallout.campusview.indiana.edu> from John Fieber at "Feb 2, 97 09:34:46 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> Currently we have an uncomfortable mix of classification based on > "what it is" and "what it is used for". While the latter seems > like it would be useful on the surface, it quickly degenerates > into a useless mess when you try and scale it up, or artificats > with open-ended uses enter the picture. It is easy to define > what Java is (a programming language) but impossible to > exhaustively define what it is used for. WWW? Games? GUI > development? Database? None of these are wrong, but where do you > draw the line? The only sane thing to do from a classification > standpoint is to fall back to intrinsic qualities of the > artifiact in question: Java is a programming language. SAWT is a > windowing API implementation. The closest thing we have to that > is devel. > > Okay, I'll shut up now. :) > > -john > Might I suggest that it makes more sense to locate a port according to what it actually is, and expand the CATEGORIES line to include various possible additional uses. This seems to be the designed intention. In this case, devel/sawt with CATEGORIES= devel www Does this make similar sense to anyone else? Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702030326.DAA28432>