Thava Alagu wrote: > > OK, if that is preferable, I will go with SUNWphppgadmin-main
Very much not preferable. While your source will still build SysV packages in the transition period, keep in mind the final package name you'll want users to be able to access via IPS. > I don't think these belong here. phppgadmin does not *depend* on > Apache. It could in principle be used with another PHP capable > webserver (I presume). > > I think having this dependency makes the life easier in most > common situations. > Though, this can in principle, be used with any PHP capable > webserver, it is better > to point to specific dependency so that users can automatically > install the dependencies > and ready to go. That's why I'm wondering if you might want to deliver the apache glue (apache-specific config) in a dedicated package and only that package depends on all the relevant apache packages. Users who want to use phpPgAdmin with, say, JES Web Server can install your core package but not your apache glue package and instead configure it themselves for their web server. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
