Re: do we have to wait for PHP 4.3 port?
# [EMAIL PROTECTED] / 2002-12-31 01:35:06 -0500: Brian [EMAIL PROTECTED] writes: BTW I'd love to see sendmail and named removed from the installs and moved to ports/packages only. Lots of people say that, but no one's done the work yet. It's a *huge* amount of work, if you think about it: being able to deliver daily reports is a critical function, Warning: you *must* install an MTA for the system to function properly! Take a look at /usr/ports/mail. :) and while most systems don't need named, other essential resolver tools can't be easily separated from the rest of BIND. other essential resolver tools... what are they? are you talking about dig and other commad line tools, or the library? DJB has released his resolver library into public domain, and it's easily separated from the rest of djbdns. :) Maybe that could help the issue? :) -- If you cc me or remove the list(s) completely I'll most likely ignore your message.see http://www.eyrie.org./~eagle/faqs/questions.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: do we have to wait for PHP 4.3 port?
On Mon, Dec 30, 2002 at 10:19:20PM -0600, Dan Nelson wrote: In the last episode (Dec 30), Brian said: hmm code freeze applies to ports as well, that is surprising. Ports and packages get put on -RELEASE cds just like kernel and userland; they get the same code-freeze treatment. Yeah, but they don't usually go on a 1+ month code-freeze when a 4.x-RELEASE comes out. -- Jonathan Chen [EMAIL PROTECTED] -- You can get farther with a kind word and a gun than you can with a kind word alone - Al Capone To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: do we have to wait for PHP 4.3 port?
On 30 Dec Brian wrote: BTW I'd love to see sendmail and named removed from the installs and moved to ports/packages only. I hope not. I like sendmail and bind and getting them out-of-the-box is perfect for me ;-)) -- dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.7 ++ Debian GNU/Linux (Woody) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: do we have to wait for PHP 4.3 port?
Jonathan Chen wrote: On Mon, Dec 30, 2002 at 10:19:20PM -0600, Dan Nelson wrote: In the last episode (Dec 30), Brian said: hmm code freeze applies to ports as well, that is surprising. Ports and packages get put on -RELEASE cds just like kernel and userland; they get the same code-freeze treatment. Yeah, but they don't usually go on a 1+ month code-freeze when a 4.x-RELEASE comes out. 5.0 is a more complex beast than the 4.x releases were, which might explain why it has taken as long as it has and why the freeze is as long as it is. I find it's never a good idea to complain about how long it takes someone to do the job right the first time. -- Paul Beard: seeking UNIX/internet engineering work http://paulbeard.no-ip.org/paulbeard.html 8040 27th Ave NE Seattle WA 98115 / 206 529 8400 Life, loathe it or ignore it, you can't like it. -- Marvin, Hitchhiker's Guide to the Galaxy To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
do we have to wait for PHP 4.3 port?
Sorry: new to FreeBSD (was an OpenBSD guy before this). I'm impressed with how fast FreeBSD puts new releases into its ports tree. Now that PHP 4.3 is out, I'm dying to use its new features, so I'm wondering if anyone knows a guesstimate on how long it should take for PHP 4.3 to be in the cvsup'd ports tree (/usr/ports/www/mod_php4) Or - can we just use the new tarball of the source, somehow with the existing Makefile + port? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: do we have to wait for PHP 4.3 port?
BSD baby wrote: Sorry: new to FreeBSD (was an OpenBSD guy before this). I'm impressed with how fast FreeBSD puts new releases into its ports tree. Now that PHP 4.3 is out, I'm dying to use its new features, so I'm wondering if anyone knows a guesstimate on how long it should take for PHP 4.3 to be in the cvsup'd ports tree (/usr/ports/www/mod_php4) I wouldn't be surprised to see it in the tree when the code freeze is lifted: that's about 2 weeks off, so you may want to install from source now and do the ports/pkg housekeeping later. -- Paul Beard: seeking UNIX/internet engineering work http://paulbeard.no-ip.org/paulbeard.html 8040 27th Ave NE Seattle WA 98115 / 206 529 8400 If a listener nods his head when you're explaining your program, wake him up. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: do we have to wait for PHP 4.3 port?
hmm code freeze applies to ports as well, that is surprising. Bri - Original Message - From: paul beard [EMAIL PROTECTED] To: BSD baby [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, December 30, 2002 7:55 PM Subject: Re: do we have to wait for PHP 4.3 port? BSD baby wrote: Sorry: new to FreeBSD (was an OpenBSD guy before this). I'm impressed with how fast FreeBSD puts new releases into its ports tree. Now that PHP 4.3 is out, I'm dying to use its new features, so I'm wondering if anyone knows a guesstimate on how long it should take for PHP 4.3 to be in the cvsup'd ports tree (/usr/ports/www/mod_php4) I wouldn't be surprised to see it in the tree when the code freeze is lifted: that's about 2 weeks off, so you may want to install from source now and do the ports/pkg housekeeping later. -- Paul Beard: seeking UNIX/internet engineering work http://paulbeard.no-ip.org/paulbeard.html 8040 27th Ave NE Seattle WA 98115 / 206 529 8400 If a listener nods his head when you're explaining your program, wake him up. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: do we have to wait for PHP 4.3 port?
Brian [EMAIL PROTECTED] writes: hmm code freeze applies to ports as well, that is surprising. Why would it be surprising? They get shipped together, they need to be consistent with each other and verified to build at that time. It's just decent release engineering. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: do we have to wait for PHP 4.3 port?
In the last episode (Dec 30), Brian said: hmm code freeze applies to ports as well, that is surprising. Ports and packages get put on -RELEASE cds just like kernel and userland; they get the same code-freeze treatment. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: do we have to wait for PHP 4.3 port?
Because ports are really config files to obtain and install other peoples software. Ports that would be deemed critical to system operation, like perl, I could see freezing those. But all ports? BTW I'd love to see sendmail and named removed from the installs and moved to ports/packages only. Bri - Original Message - From: Lowell Gilbert [EMAIL PROTECTED] To: Brian [EMAIL PROTECTED] Cc: paul beard [EMAIL PROTECTED]; BSD baby [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, December 30, 2002 8:17 PM Subject: Re: do we have to wait for PHP 4.3 port? Brian [EMAIL PROTECTED] writes: hmm code freeze applies to ports as well, that is surprising. Why would it be surprising? They get shipped together, they need to be consistent with each other and verified to build at that time. It's just decent release engineering. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: do we have to wait for PHP 4.3 port?
Brian [EMAIL PROTECTED] writes: Because ports are really config files to obtain and install other peoples software. Ports that would be deemed critical to system operation, like perl, I could see freezing those. But all ports? The number of ports that are mission-critical to *somebody* numbers in the hundreds, perhaps thousands. You were asking about PHP; to risk shipping an official FreeBSD release without a full release process on the PHP port would be negligent. BTW I'd love to see sendmail and named removed from the installs and moved to ports/packages only. Lots of people say that, but no one's done the work yet. It's a *huge* amount of work, if you think about it: being able to deliver daily reports is a critical function, and while most systems don't need named, other essential resolver tools can't be easily separated from the rest of BIND. But this has all been covered before, at great length; if you're interested in taking the task on, see the mailing list archives. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
