Date: Thu, 02 May 1996 01:11:39 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: knarf@camelot.de (Frank Bartels) Cc: freebsd-ports@freebsd.org Subject: Re: -current-ports under -RELEASE Message-ID: <18830.831024699@time.cdrom.com> In-Reply-To: Your message of "02 May 1996 07:49:44 GMT." <4m9peo$hf0@lancelot.camelot.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> I think the -current-ports should work under the _latest_ release and > if that is not possible, there should be a flag or something which > says it is impossible to compile this port under -RELEASE, perhaps > with a small explanation... I think the flag idea is not just a bad idea - this issue has come up before, and Satoshi usually makes the fair point that if he had to try and track ports changes between both 2.2 and in 2.1-R, he'd go insane. Setting a flag which says "this only works in release blah or later" might be a nice compromise. Maybe a regexp which matches against the output of `uname -r', so you can get fancy if you've got a port which runs against a truly select set of releases. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18830.831024699>