maria-developers team mailing list archive

[worklog-noreply@xxxxxxxxxxxx]

-----------------------------------------------------------------------
                              WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...........: Good defaults for ./configure (for end-user source builds)
CREATION DATE..: Thu, 19 Aug 2010, 10:09
SUPERVISOR.....: 
IMPLEMENTOR....: 
COPIES TO......: 
CATEGORY.......: Server-RawIdeaBin
TASK ID........: 130 (http://askmonty.org/worklog/?tid=130)
VERSION........: Server-9.x
STATUS.........: Un-Assigned
PRIORITY.......: 60
WORKED HOURS...: 0
ESTIMATE.......: 0 (hours remain)
ORIG. ESTIMATE.: 0

PROGRESS NOTES:



DESCRIPTION:

I would really like it to be easy to build MariaDB from source.

Basically, a plain ./configure should just work in the normal case, and
produce something sensible that is close/identical to what a relase build
looks like.

Unfortunately, this is not currently so. There is a long tradition in MySQL
(and now MariaDB) that release builds are made with a long carefully crafted
list of ./configure options that are necessary to get everything included or
enabled.

One concrete example I found is that plain ./configure will build
XtraDB/InnoDB as plugins by default. This means that upon starting the server,
there will be no engine "innodb" available until one is installed with INSTALL
PLUGIN! I think this is not desirable default behaviour.

The task here is to go through the ourdelta build scripts [1] and check all
the ./configure options we use in them and what the default behaviour of that
option is. Defaults that is not sensible for a plain ./configure build should
be changed.

References:

[1]
http://bazaar.launchpad.net/~maria-captains/ourdelta/ourdelta-montyprogram-fixes/files


ESTIMATED WORK TIME

ESTIMATED COMPLETION DATE
-----------------------------------------------------------------------
WorkLog (v4.0.0)