Date: Fri, 05 May 1995 11:36:58 -0700 From: Paul Traina <pst@shockwave.com> To: Adam David <adam@veda.is> Cc: ache@astral.msk.su, CVS-commiters@freefall.cdrom.com, cvs-ports@freefall.cdrom.com, torstenb@freefall.cdrom.com Subject: Re: cvs commit: ports/news/inn/pkg PLIST Message-ID: <199505051836.LAA01898@precipice.shockwave.com> In-Reply-To: Your message of "Fri, 05 May 1995 18:24:26 -0000." <199505051824.SAA20758@veda.is>
next in thread | previous in thread | raw e-mail | index | archive | help
Let me rephrase this. What does renaming /var/spool/news to /var/news fix? Are we just doing it to follow our OWN convention? /usr/spool/news was broken because /usr/spool was stupid for diskless machines /usr/spool/mail was broken because /usr/spool was stupid for diskless machines /var/spool/mail was NOT broken /var/spool/news is NOT broken /var/mail is stupid, but it was done in the 4.4 distribution, so we leave it as is because most programs will look there these days when auto-configuring /var/news is stupid, we're doing it ourselves, we'll have to fix every piece of news related software that looks for /var/spool/news and we're just making porting and maintenance that much more of a pain. Again, what are we fixing? We need to look at the cost benefit ratio of making gratuitous changes. Why are we trying to make FreeBSD = !BSD? If I wanted to run !BSD, I'd run Linux (vomit). From: Adam David <adam@veda.is> Subject: Re: cvs commit: ports/news/inn/pkg PLIST > Is /var/spool/news broken? It's really a convention better left unchanged. It is as broken as /var/spool/mail, which is also a convention. :) -- Adam David <adam@veda.is>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505051836.LAA01898>