hey steve,
On Thu, Jun 30, 2005 at 01:38:11AM -0400, Stephen Gran wrote:
> These seem to me to be the same thing - if they answer "yes, do the work
> with debconf", and then remove the app, the remove question gets a yes.
> I don't think we need a seperate question. After all, the app is gone,
> and the real config files should not be stored in apache/conf.d anyway,
> just the symlinks. Remove the symlinks if the "manage with debconf"
> is a yes, and I think we're OK.
you're probably right here. this is a side effect of my based these
questions off of what i put together in dbconfig-common, where it
makes more sense to have two decisions.
> > Template: webapps-common/install_error
> >
> > Template: webapps-common/remove_error
>
> These look fine. I'll let those who have an eye for grammar and the
> like (bubulle strikes me as someone to talk to - he has a very good ear
> for template language).
believe it or not, bubulle helped me develop the original versions of
these questions (again, in dbconfig-common). after things have settled
with these templates, i'll send this to the translation lists for
review too.
> > Template: webapps-common/httpd/select_httpd
>
> Fine, although the possibilities could be preselected - ISTR some apps
> asking if I wanted to install for apache-perl when it's not installed.
> that seems unnecessary. A simple test for /usr/share/doc/${pkg} before
> filling the string should do.
what i was planning on doing was having a list of supported httpds
internal in the code somewhere, and populating the choices at run-time
with that. additionally, the choices could be verified for their
installation status and non-installed choices could be somehow
differentiated in the list (like being preceded by a !), and/or the
installed choices could be selected by default.
> > Template: webapps-common/httpd/virtualhost_new
> >
> > Template: webapps-common/httpd/virtualhost
> >
> > Template: webapps-common/httpd/virtualhost_more
> >
> > Template: webapps-common/httpd/site_directory
>
> Can these possibly be autodetected? Something like checking for
> directories that look like FQDN under /srv/www and parsing httpd.conf?
it'd probably be a bit of a clunky shell script, but would certainly
be possible. you'd need to read httpd.conf, as well as all files and
directories Include'd, and then grab out all the <VirtualHost></VirtualHost>
blocks, and then from those grab all the ServerName settings... i think...
> I realize this is some work (I'm happy to hack on it in the next few
> weeks, when I'm on enforced vacation, if you think it's a good idea).
well, i'd be a hypocrite if i were to chastise you for working on debian
during vacation as i'm frequently guilty of the same :) if you
are interested in doing this, could you write a /bin/sh function
that does what's described above (or whatever really needs to be done)?
i could then include it with the other internal httpd functions in
webapps common.
sean
--
Attachment:
signature.asc
Description: Digital signature