[Typo3-dev] TYPO3core autotools integration and doxygen

Mathias Schreiber [wmdb] mathias.schreiber at wmdb.de
Wed Mar 23 08:38:28 CET 2005


Sven Wilhelm wrote:
> As I wrote in a previous post, that comes in the same way. During 
> integrating that stuff, I added a packaging directory to the core that 
> holds all distribution specific stuff, currently in developing for 
> Debian, Fedora - planned for MacOSX, perhaps also for Solaris.
> (Sorry, no Windows support currently planned from my side :)

So we would drop the benefit of being platform independent.


> One more word to autoconf as it seems to me that there are people who 
> not know when this is used.
> 
> In projects where autoconf is used the release manager checks out a copy 
> from cvs (or other rcs), runs autoconf,... (typically called due 
> something like autogen.sh or bootstrap.sh) and calls 'make dist' to 
> generate a tar.(gz|bz2) file which is the base for packaging.

typo3.sunsite.dk?
I have to admit that I have no idea what autoconf is and what it could 
be used for.
Maybe you could clear things up for me by writing down a reasonable 
scenario?

> During calling the ./configure in the packaging stuff several 
> placeholders are substituted.

The only thing where Typo3 Installs differ from each other are 
localconf.php settings.

We have a small PHP script where I enter the domain name of a Website 
and its name, a password and hit "generate" in a browser.
In background the script acts as follows:
- Generate directory on the server
- untar selected typo3 version source
- untar selected typo3 dummy site
- mv "dummy-[TYPO3-VERSION] "www" (cause our install dir is called www)
- deletes all symlinks and sets them differently (since I don't like 
Stucki's way of setting them, sorry pal ;-))
- Install database
- Delete Admin User
- Generate Admin users for everybody in our company
- Setting IM paths right in localconf.php
- setting certain parameters (like doNotCheckReferer or devIPMask)

Then I have to set up the new domain in the DNS and set up the apache 
vhosts file, reload apache and I can log into a generalized, standarized 
typo3 website

Something like this?

-- 
No Subject - No Realname - No Service!
Respect the List/Newsgroup Rules!
  >> http://typo3.org/1438.0.html <<




More information about the TYPO3-dev mailing list