Thava Alagu wrote: > > The main reason is that, I don't want this to be enabled by > default by httpd daemon, > or atleast if someone decides to enable only core configs (like php > module) and not > phppgadmin, I want to make that easier. The default apache config file > does > include conf.d/*.conf, if some one decides, they don't want > phppgadmin, then > they need to list all config files in conf.d except phppgadmin.
But you could argue if someone installs the apache config for phppgadmin, it must be because they want it. Reviewing the thread, it seems your options are - Everything (including apache config) in one package. Forces the pkg to depend on apache even though users might use a different server. Here you can still decide between samples-conf.d and conf.d but probably the former, so one can install it and use elsewhere. - All content in one package and apache-config in separate package (into conf.d). If one installs the apache-config package it's because it will be used with apache, otherwise install only content and handcraft configuration elsewhere. Any other options? Since the thread has gone for a while, please post the latest revision so there is a concrete proposal to review. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
