Jyri Virkki wrote: > Seema Alevoor wrote: >> Fine. Let us have conf.d (new empty directory) under /etc/apache2 . > > Why would it be empty? If that's the one and only editable conf > directory, surely there will be something there? > > If you look at the apache2 currently in the sources, a number of conf > files are installed, some are copied as-is and some are copied with > modifications. All those files, at least (or more - since a goal of Web > Stack is to enhance functionality and improve out of box experience) > will be there in the directory containing conf files. > > Could you expand on why you see conf.d being empty?
This is a place holder. It was high lighted in the previous discussions that the existing extra contains many conf files which are not of much use. So, the plan was to carefully select task specific conf files. Till we identify these files, this dir will be empty. -- Seema.
