[Mailman-Users] Config_list doesn't copy the "Public HTML Pages"

[David Dyer-Bennet]

On 9/6/06, Brad Knowles <brad at stop.mail-abuse.org> wrote:

> The templates are stored in the filesystem, in a variety of different
> places depending on whether you're talking about the standard
> as-shipped language dependent versions, the standard as-shipped
> language independent versions, the site-wide language independent
> versions, site-wide language dependent versions, list-specific
> language independent versions, or list-specific language dependent
> versions, and that's just the six different potential combinations
> that I can come up with off the top of my head -- I'm pretty sure
> that there are some others that I haven't thought of.

I didn't even know there *were* list-specific versions of that; could
you tell me where they end up if they're created?  (I hadn't
customized my fake installation at the list level, so the directories
probably didn't exist in it, so I didn't find them, is my immediate
guess.   I'm currently doing my customizing at the top level.  Not
that it matters in a temporary installation used once to transform old
archive mbox files into the html archive pages; but it's *inelegant*
and I should fix it.

> How you would pick and choose which specific templates are to be
> considered as part of the configuration for a given list would be a
> complex subject.  Do you copy the site-wide versions or not?  If you
> do copy them, do you install them in the list-specific locations on
> the other end, or do you install them in the appropriate site-wide
> location?  And what if there are conflicts?

Yes, this is potentially a conflict.  Although if you're copying a
list within a site, the site-level stuff above it will remain the
same.

A scheme that copied the list-specific stuff across all langugages
when a list was copied would probably be very usable.

> This starts to get real messy, real quick.
>
> >  But config_list knows only about a subset of configuration variables.
>
> Right.  My understanding is that templates are not considered part of
> a list configuration, and config_list has always seemed to me to be
> kind of a quick-n-dirty tool, and never intended to be a
> be-all/do-all 1000000% perfect list duplication management system.

I see stuff about expanding (and making less weirdly inconsistent!)
the template scheme as future work items.   We should check and see if
that includes addressing the issue of copying a list in a more elegant
way.
-- 
David Dyer-Bennet, <mailto:dd-b at dd-b.net>, <http://www.dd-b.net/dd-b/>
RKBA: <http://www.dd-b.net/carry/>
Pics: <http://www.dd-b.net/dd-b/SnapshotAlbum/>
Dragaera/Steven Brust: <http://dragaera.info/>