[MKDoc-dev] Improving MKDoc Installation

[Chris Swaine]

Hiya,

Well as just a humble user and not techie I am now totally lost, so will bow
out of this! To some degree this re-enforces one of my original points which
is, who this CMS for? Who are you targetting it at - who are your actual
users and what are your drivers? There is always a risk that it will never
get rolled out to the masses as it is fundementally a developers project
which will just remain in developer land! Do you make the product fit the
user - or the user fit the product?

Food for thought.

Have fun!

with very best regards...Chris...

Home:
Chris Swaine
105 Silchester Road
Southcote
Reading
RG30 3EJ
Tel: 0118 9391736
Email: chris at reading-city.net
----- Original Message ----- 
From: "Sam Tregar" <sam at tregar.com>
To: "Chris Croome" <chris at webarchitects.co.uk>
Cc: <mkdoc-dev at lists.webarch.co.uk>
Sent: Friday, September 24, 2004 1:45 AM
Subject: Re: [MKDoc-dev] Improving MKDoc Installation


> On Thu, 23 Sep 2004, Chris Croome wrote:
>
> > I see the Krang way of doing this as an interim way of making things
> > easier prior to getting the native packages sorted out.
>
> As a side note, people on the Krang project are also interested in
> getting native package distribution working.  I'm now wondering if
> there's some way to separate the Krang installation system out as a
> separate project that could be used to install any Apache/mod_perl
> app.  Then we could add native package generation support to that
> system and kill n-birds with 1 stone.
>
> > One thing I'm not sure about with Sam's suggestion is how to deal
> > with native CPAN packages being installed or not, for example Petal
> > is packages for debian already and there are a lot of the CPAN
> > modules that are needed packaged for Fedora (eg XML:RSS) by 3rd
> > parties (DAG, Freshrpms etc) and many people will be using these
> > repos already...
>
> I think it would be possible to add support for using native CPAN
> packages in place of building and installing.  Actually, I think it
> would be no harder than a few lines of code added to the
> platform-support module.  In Krang each supported platform has a
> module which inherits from Krang::Platform and can override methods to
> implement platform-specific features.
>
> > The tricky issue thougih is apache and mod_perl, currently apache 1.3
> > is required and many distros, like Fedora, ship with apache 2... so
> > a new apache and mod_perl does need to be complied from source.
>
> Another problem is that Apache 1.3 is often compiled to load mod_perl
> as a DSO which leads to cronic instability.
>
> > It could be that it would be easier to target debian for native
> > packages since I expect they will be using apache 1.3 for the
> > forseeable future...
>
> Porting Bricolage to Debian was an amazingly difficult job.  Debian
> has the strangest Apache install I've ever seen.  For better or worse
> Apache is an extremely flexible piece of software and it's really
> unbelievable how many different ways there are to compile and
> configure it!
>
> -sam
>
>
> _______________________________________________
> MKDoc-dev mailing list
> MKDoc-dev at lists.webarch.co.uk
> http://lists.webarch.co.uk/mailman/listinfo/mkdoc-dev