Re: php5 Portfile question

James,

thanks for your answer. I understand this is a volunteer effort, so  
I'll volunteer to clean up the php5 portfile (unless there are  
objections).

Let me clarify my comments on CLI.  By default the portfile is  
creating a binary that when executed ("/path/to/php -v") it returns  
something like:

PHP 4.3.11 (cli) (built: Dec  9 2005 11:10:27)
Copyright (c) 1997-2004 The PHP Group
Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies

(I used the default OSX 10.4.5 /usr/bin/php to generate this output.)

As you likely know, the php-cli binary is for interactive use or  
shell-script style use. This doesn't matter to Apache because it uses  
the mod_php stuff. As far as I know it builds the appropriate  
binaries for Apache correctly though I haven't run apache at all to  
verify.

Lighttpd's mod_fastcgi requires that php be built for cgi-fastcgi  
use. It chokes something terrible on the CLI binary since its  
behavior is different from lighttpd's expectations. So, I built my  
own php with the various switches necessary for fastcgi and therefore  
get:

PHP 5.1.2 (cgi-fcgi) (built: Feb 28 2006 15:18:59)
Copyright (c) 1997-2006 The PHP Group

Re: php5 Portfile question

On Feb 28, 2006, at 4:19 PM, Chuck Remes wrote:

> James,
>
> thanks for your answer. I understand this is a volunteer effort, so  
> I'll volunteer to clean up the php5 portfile (unless there are  
> objections).

Thanks Chuck. We'd love to have your help on it.

>
> Let me clarify my comments on CLI.  By default the portfile is  
> creating a binary that when executed ("/path/to/php -v") it returns  
> something like:
>
> PHP 4.3.11 (cli) (built: Dec  9 2005 11:10:27)
> Copyright (c) 1997-2004 The PHP Group
> Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies
>
> (I used the default OSX 10.4.5 /usr/bin/php to generate this output.)
>
> As you likely know, the php-cli binary is for interactive use or  
> shell-script style use. This doesn't matter to Apache because it  
> uses the mod_php stuff. As far as I know it builds the appropriate  
> binaries for Apache correctly though I haven't run apache at all to  
> verify.

As I recall, build of the cli was recently added due to user  
requests. (unless I'm confusing that with another port,  which is  

Re: X11R6 flavors

On Feb 28, 2006, at 1:08 AM, Yves de Champlain wrote:

> XFree86 is made so you can install it on top of Apple's and get  
> XDarwin and X11.app / quartz-wm running.  The stopper is DP will  
> not want to overwrite existing files, although it can be forced to  
> (port -f install XFree86)

Fink's web site had me believing the binaries were incompatible, but  
I wasn't sure if that's because Fink distributes binaries or if it's  
because the way things compile.

My last question is, will I be able to run X without running Aqua?  
(can I log into the console, type startx, and use just X Windows?)

Re: X11R6 flavors

On Feb 28, 2006, at 11:11 PM, James Ashenhurst wrote:

> My last question is, will I be able to run X without running Aqua?  
> (can I log into the console, type startx, and use just X Windows?)

The rest of this is, "because when I run startx from the console Aqua  
seems to start up and freeze, and I thought it was because Apple's  
X11 doesn't work that way but maybe it's because I have the wrong  
setting somewhere."

Re: X11R6 flavors

On 2/21/06, James Ashenhurst <jashenhu <at> cs.oberlin.edu> wrote:

> http://fink.sourceforge.net/doc/x11/inst-xfree86.php?phpLang=en
> > If you use the xfree86 package, and later switch to Apple's X11 (on
> > either 10.2.x or 10.3.x), any packages you have built against
> > xfree86 will need to be rebuilt, as the binaries are incompatible.
>
> I assume this works both ways. Does this mean that I have to
> recompile all my X programs, or just the ones that identify
> themselves as being directly dependent on XFree86 (e.g. I recompile
> GTK, but anything that uses GTK doesn't have to be compiled)?

You assume wrong.  ;)

You can always run binaries on a newer X11 if they were built against
an older X11.  So if you built stuff against apple's x11, you've
effectively built them against XFree86 4.4.  Those binaries should be
compatible with XFree86 4.4 or 4.5, or x.org 6.7 or higher.  But if
you were to build against, say, xfree86 4.5, you can't run them on
xfree86 4.4 (or apple's x11) since the binaries will reference library
symbols that were created between the 4.4 and 4.5 release.

_______________________________________________
Darwinports mailing list
Darwinports <at> opendarwin.org
http://www.opendarwin.org/mailman/listinfo/darwinports

Re: X11R6 flavors

Le 06-02-28 à 23:11, James Ashenhurst a écrit :

> On Feb 28, 2006, at 1:08 AM, Yves de Champlain wrote:
>
>> XFree86 is made so you can install it on top of Apple's and get  
>> XDarwin and X11.app / quartz-wm running.  The stopper is DP will  
>> not want to overwrite existing files, although it can be forced to  
>> (port -f install XFree86)
>
> Fink's web site had me believing the binaries were incompatible,  
> but I wasn't sure if that's because Fink distributes binaries or if  
> it's because the way things compile.

It's because of how things link, I believe.  Apple uses its Framworks  
where XFree86 uses its own libraries, i.e. for OpenGL

>
> My last question is, will I be able to run X without running Aqua?  
> (can I log into the console, type startx, and use just X Windows?)

As far as I know, console login is broken on 10.4 (or inexistent, I  
don't remember) and Aqua-less XFree86 does not work on many hardware  
configurations with Tiger / Darwin 8, like my 17" flat panel iMac,  
for example.

yves

"Getting Started" guide complete!

After a long interruption, I've finally completed the newbie Getting  
Started guide, which can be found here:

http://wiki.opendarwin.org/index.php/DarwinPorts:Getting_Started

I've also added a link to this guide on the DP Wiki home page.

Please let me know how we can improve this guide keeping in mind its  
target audience is the non-Unix (and non-DarwinPorts) savvy. I'd like  
to work towards assembling all of these various documents in a useful  
way to replace the "Documentation" link on our site to all of these  
various docs designed for different purposes.

Your help is very useful. It's sometimes hard finding large  
uninterrupted blocks of time to devote to something like this.

-----------
Joe Auty
NetMusician: web publishing software for musicians
http://www.netmusician.org
joe <at> netmusician.org

Re: "Getting Started" guide complete!

On Tue, 28 Feb 2006 21:21:15 -0800, Joe Auty <joe <at> opendarwin.org> wrote:

> After a long interruption, I've finally completed the newbie Getting  
> Started guide, which can be found here:
>
>
> http://wiki.opendarwin.org/index.php/DarwinPorts:Getting_Started
>
>
> I've also added a link to this guide on the DP Wiki home page.
>
>
> Please let me know how we can improve this guide keeping in mind its  
> target audience is the non-Unix (and non-DarwinPorts) savvy. I'd like to  
> work towards assembling all of these various documents in a useful way  
> to replace the "Documentation" link on our site to all of these various  
> docs designed for different purposes.
>
> Your help is very useful. It's sometimes hard finding large  
> uninterrupted blocks of time to devote to something like this.

Nice work!

Just curious, the guide says:

"It can be confusing to figure out what each variant enables, but if you  
are confused you can ask the port maintainer or the DarwinPorts mailing  
list."

Would it be hard to add a one-line description on each variant that could  

Re: Problem with upgrading eog with last upgrade

On Mar 1, 2006, at 12:33 AM, Daniel J. Luke wrote:

> On Feb 28, 2006, at 6:27 PM, Edward Thome wrote:
>> Is this due to an error in the perl58 upgrade, and what need I do,  
>> please?
>
> Currently darwinports isn't able to automatically track that all of  
> your perl modules need to be rebuilt when you upgrade perl ...
>
> you need to uninstall and remove (clean --all) each of the  
> installed p5-<whatever> ports and re-install them.

On HEAD this could be solved like this:

port -R upgrade perl5.8; port upgrade outdated

Re: "Getting Started" guide complete!

On 2006-02-28 22:06:55 -0800, Alexander Limi wrote:
> Would it be hard to add a one-line description on each variant that
> could be printed if you did something like:
> 
> $ port info subversion
> subversion 1.3.0, Revision 2, devel/subversion
> Variants:
> +no_neon (Builds without HTTP and WebDAV support)
> +no_bdb (Uses FSFS as storage instead of BDB)
> +mac-os-x-server-mod_dav_svn (Builds against the Apple-supplied apache2 in  
> /opt/apache2 and thus may have problems that the normal variant will not  
> have)

This would be very useful.

Also, could one have access to the changelogs?

--

-- 
Vincent Lefèvre <vincent <at> vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA