UNIX admin wrote: > > For my part, I would very much like to see php be available as /usr/bin/php. > > What is the final consensus on this matter?
No formal consensus, but I filed an RFE to track the change. When someone gets to making the code changes and posts the code review, it'll probably be approved. It should get recorded in a relevant ARC case as well, though I don't really expect opposition there either. There's a lot of process for seemingly simple changes, which is why the answer to "final consensus" isn't so straighforward... But I wouldn't expect adding this to be a problem, just a matter of doing it. > In my experience, for PHP, making a distinction between "php4" and > "php5" is enough. Good to hear. > With this in mind, I propose that the packages be renamed before > Nevada is solidified into the next release of Solaris. Current > naming is "SUNWphp520", whereas in my experience "SUNWphp5r" and > "SUNWphp5u" would have been just fine (and elegant). At the very least I'd like to see it versioned at the "5.2" (5.2.*) level, but if versioning it as 5 (5.*.*) is possible, that would be ideal. I didn't use PHP prior to php5 so I can't comment on enough of its compatibility history but I'd like to hear from others here who've used it long enough so we can gather enough data to go one way or the other. > What I'm wondering is, is there any way to combine our efforts, so > that there is no duplication of work? > > For my part I can offer extensive experience getting open source > software to compile & link on Solaris with Sun Studio compilers, and > I also have extensive experience producing Solaris System V > packages. Certainly, input/help is welcome! Various approaches are possible depending on your time and preferences. As others work on various pieces, there will be discussion threads here (and later, code reviews). You can share your experiences during those discussions and help direct the integrated components in directions that meet your needs (so you won't have to duplicate them). For a more hands-on approach, you could download the source tree (see http://www.opensolaris.org/os/project/webstack/files/), experiment with it locally, adding build options (say, 64 bit), testing the changes on your systems and sharing patches here showing what works (and what doesn't). Or you could even take ownership of delivering some component, it means a lot of process work but it can be done. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
