Danek Duvall wrote: > On Tue, Nov 13, 2007 at 03:00:16PM -0800, Sriram Natarajan wrote: > > >> Peter >> This is definitely a very valid issue and we are very much aware of it. The >> best way to solve this is to deliver different PHP extensions in different >> packages in the same way as is being currently done on Linux platforms. At >> this point, we want to tackle the most important issue of delivering a >> complete stack. Once Web Stack project adopts Image Packaging System >> (http://opensolaris.org/os/project/pkg/) , we could deliver different PHP >> extensions in different packages to limit unnecessary dependencies like >> this. >> > > Um, there's nothing that IPS does to solve this problem that SVr4 packages > can't do for you right now. Just put the various bits into separate > packages. Done. > > The only thing is for each extension, we need to deliver a 'usr' and 'root' package. I guess, with IPS, we don't have that restriction. So, we want to split our packages at the time of adopting IPS. > Now, if, as Peter suggested, you're building everything in as hard > dependencies in the ELF objects -- i.e., PHP will refuse to run if it > doesn't have everything available -- then you have a problem no packaging > system will solve for you. > No, we don't have such dependency > And I strongly suggest that you make sure not to integrate with that > problem. Requiring a few small things that are almost certain to be on > the system anyway is probably just fine. Requiring a couple hundred megs > of seriously optional stuff, not fine. > > At this point, we simply require couple hundred megs dependency but there are no hard coded dependency on packages like Postgres or MySQL.
thanks sriram -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/webstack-discuss/attachments/20071114/c629fb00/attachment.html>
