I'm not sure if this is how it's supposed to work, or not, but
that's why I'm asking.
I just installed MM 2.0.8. Went into $prefix/Mailman/mm_cfg.py and
added a DEFAULT_HOST_NAME and DEFAULT_URL. When I pointed my browser to
/mailman/admin, the header and body text correctly displayed
On October 12, 2001 05:48 am, Oliver Egginger wrote:
> Hello,
>
> mm_cfg.py is relevant only within the list creation process.
> The default host name is a very basic thing and should be set via a
> configure option. I was thinking that one of the options
> --build, --host or --target could do thi
Hello,
mm_cfg.py is relevant only within the list creation process.
The default host name is a very basic thing and should be set via a configure option.
I was thinking that one of the options
--build, --host or --target could do this.
If I would use mm_cfg.py instead,
this wouldn't change the
At 17:15 + 10/11/2001, Oliver Egginger wrote:
>Only set this value in Default.py had the desired effect.
>But is overwitten by every new instalation.
Which is why the file mm_cfg.py is provided. Its contents override the
stuff in Defaults.py, and it is left alone by the Mailman-recommended
i
On 11 October 2001, Oliver Egginger said:
> This isn't a big problem ...
>
> I need to change the default Hostname.
> The Configure options:
> --build
> --host
> --target
> didn't what is requested.
What does "./configure --help" say about those options?
> Only set this value in Default.py had
This isn't a big problem ...
I need to change the default Hostname.
The Configure options:
--build
--host
--target
didn't what is requested.
Only set this value in Default.py had the desired effect.
But is overwitten by every new instalation.
- oliver
-
