GSOC Proposal: Bricolage INSTALLER (v-2)---- Pranava Swaroop S

Hi,

My second iteration:

~~~~~~~~~~~~~~~~~~
Pranava Swaroop S
pmadhyasthaacm.org
~~~~~~~~~~~~~~~~~~

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
REJUVENATING THE INSTALLER FOR BRICOLAGE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Greetings!

I quote from "Bricolage" website:

"Bricolage, an open-source enterprise-class content
management system,
greatly simplifies the complex tasks of creating, managing,
and
publishing the vast libraries of content essential to any
organization."

I wish to take the improvement of the installer and the
development of
the modules associated with Bricolage as a part of the
Google's Summer
of Code initiative. This project will help resolve most of
the
installer based problems of Bricolage.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Benefits to the Bricolage Community
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This project would simplify the whole process of
installation and
would gel beautifully to the afore mentioned quote. This
project will
also enhance the usage scope of Bricolage considerably.

~~~~~~~~~~~~
Deliverables
~~~~~~~~~~~~
1. Creation of a perl build file(does the job of configuring
and
building Bricolage) with sub-modules for 'OS-Specific'
installation(with OS-specific hints in case the installation
fails)

2. Creation of a robust-user-friendly INSTALL file(which
does hassle
free 'download and install' process when a module is not
found)

3. A script to manage the database back-end during the
process of
installation(this script would also support command-line
arguments)

4. A separate upgrade script(this script would be re-written
in order
to simplify the process of updation).

5. Polishing the package to smoothen the process of
installation,
which should guarantee trouble free installation/up-dation
to the
user.

Non-Code deliverables will include documentation for all the
scripts
and modules mentioned above.

~~~~~~~~~~~~~~~
Project Details
~~~~~~~~~~~~~~~
The main objective of the project is to ease out the process
of
installation and to make the installer more user friendly,
at the same
time, making the installer noise free for the developers
too, which
should result in hassle free updation and maintenance.

The first part of the project is to make a perl-build
scripts using
CPAN based modules. This would contain Module::Build,
Locale::Maketext
for the process of building and App::Info for the
dependency
detection. The main aim here is to eliminate the standard
unix
makefiles and configuration files. Also David's FSA::Rules
module will
be used to handle decision trees. There would be verbose
comments if
at all there is an error. These should help the user to
carve the
right path.

At present, the Bricolage installer seems to have problems
in
automating many installations of important CPAN modules. The
cpan.pl
file would be rewritten to resolve such issues. Also, a new
support
for CPAN++ would be added, which would require additional
modules to
be written.

The INSTALL file with default options would be created. This
would
also support custom options which could be explicitly stated
from the
command line, when INSTALL is being called.

Creation of a database manager(to manage DB during the
install). This
database manager manages the back-end of the DB and also
creates the
databases. This script will again provide custom command
line options
which the user can provide, thereby, easing out the DB
related
process.

The upgrade script would be modified and would be made more
verbose.
The objective here is to give user the flexibility of the
upgrade and
ease of backup and restore.

Finally, other scripts which are used during the process of
installation would be optimized.

Suggestions are welcome!
~~~~~~~~~~~~~~~~
Project Schedule
~~~~~~~~~~~~~~~~
The project is planned to be split across 6 major Phases:

1. Analysis (May 26 - May 31)(I would be happy if I could
start early):
This phase involves interaction with the mentor and the key
people
involved in similar projects  in order to exactly understand
the
requirements.

2. Development Part I (June 1 - June 15):
This phase will involve the creation of the afore mentioned
build file.

3. Development Part II (June 16 - June 30):
Re-incarnation of cpan.pl and modules which would work with
CPAN++

4. Development Part III (July 01 - July 15):
Scripts and modules related to INSTALL and the INSTALL file
itself.

5. Packaging (July 15 - August 5):
Database Manager and a fresh Upgrade file and related
modules.

6. Testing and Wrap-Up (August 5 - August 21):
Thoroughly test every aspect of the finished package. This
phase will
also include the development of non-code deliverables.

~~~
Bio
~~~
I am a third-year undergraduate at the Malaviya National
Institute of
Technology, Jaipur, India. I am pursuing my B.Tech. in
Computer
Engineering at the institute. I have been passionate about
computers
since my childhood and have been a free software advocate
for around 3
years now.

I have contributed to several opensource projects, the most
prominent
among them have been Gentoo, Apertium and  Mozart. These
projects have
helped me clear most of my concepts in C and Perl. I also
am
interested in Natural Language Processing, where I have
mostly used
perl for the purpose of Regular Grammars. These I believe
are the
essential requirements for this projects. I have also
created a small
content management system and an Online Judge(code Testing
Platform)
with perl.

Finally, I would like to express my deep commitment to this
project.
You can find more details about me and the projects that I
am
currently involved in, at my
website. Please don't hesitate to contact me if any part of
this
proposal is not clear to you.

Thank you for considering this proposal, and for your time!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
My CV     : http://pranava.rsp
an.in/resume.pdf
My Website: http://pranava.rspan.in/

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Cheers

Pranava

Hi,

My second iteration:

~~~~~~~~~~~~~~~~~~
Pranava Swaroop S
pmadhyasthaacm.org
~~~~~~~~~~~~~~~~~~

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
REJUVENATING THE INSTALLER FOR BRICOLAGE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Greetings!

I quote from "Bricolage" website:

"Bricolage, an open-source enterprise-class content
management system,
greatly simplifies the complex tasks of creating, managing,
and
publishing the vast libraries of content essential to any
organization."

I wish to take the improvement of the installer and the
development of
the modules associated with Bricolage as a part of the
Google's Summer
of Code initiative. This project will help resolve most of
the
installer based problems of Bricolage.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Benefits to the Bricolage Community
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This project would simplify the whole process of
installation and
would gel beautifully to the afore mentioned quote. This
project will
also enhance the usage scope of Bricolage considerably.

~~~~~~~~~~~~
Deliverables
~~~~~~~~~~~~
1. Creation of a perl build file(does the job of configuring
and
building Bricolage) with sub-modules for 'OS-Specific'
installation(with OS-specific hints in case the installation
fails)

2. Creation of a robust-user-friendly INSTALL file(which
does hassle
free 'download and install' process when a module is not
found)

3. A script to manage the database back-end during the
process of
installation(this script would also support command-line
arguments)

4. A separate upgrade script(this script would be re-written
in order
to simplify the process of updation).

5. Polishing the package to smoothen the process of
installation,
which should guarantee trouble free installation/up-dation
to the
user.

Non-Code deliverables will include documentation for all the
scripts
and modules mentioned above.

~~~~~~~~~~~~~~~
Project Details
~~~~~~~~~~~~~~~
The main objective of the project is to ease out the process
of
installation and to make the installer more user friendly,
at the same
time, making the installer noise free for the developers
too, which
should result in hassle free updation and maintenance.

The first part of the project is to make a perl-build
scripts using
CPAN based modules. This would contain Module::Build,
Locale::Maketext
for the process of building and App::Info for the
dependency
detection. The main aim here is to eliminate the standard
unix
makefiles and configuration files. Also David's FSA::Rules
module will
be used to handle decision trees. There would be verbose
comments if
at all there is an error. These should help the user to
carve the
right path.

At present, the Bricolage installer seems to have problems
in
automating many installations of important CPAN modules. The
cpan.pl
file would be rewritten to resolve such issues. Also, a new
support
for CPAN++ would be added, which would require additional
modules to
be written.

The INSTALL file with default options would be created. This
would
also support custom options which could be explicitly stated
from the
command line, when INSTALL is being called.

Creation of a database manager(to manage DB during the
install). This
database manager manages the back-end of the DB and also
creates the
databases. This script will again provide custom command
line options
which the user can provide, thereby, easing out the DB
related
process.

The upgrade script would be modified and would be made more
verbose.
The objective here is to give user the flexibility of the
upgrade and
ease of backup and restore.

Finally, other scripts which are used during the process of
installation would be optimized.

Suggestions are welcome!
~~~~~~~~~~~~~~~~
Project Schedule
~~~~~~~~~~~~~~~~
The project is planned to be split across 6 major Phases:

1. Analysis (May 26 - May 31)(I would be happy if I could
start early):
This phase involves interaction with the mentor and the key
people
involved in similar projects  in order to exactly understand
the
requirements.

2. Development Part I (June 1 - June 15):
This phase will involve the creation of the afore mentioned
build file.

3. Development Part II (June 16 - June 30):
Re-incarnation of cpan.pl and modules which would work with
CPAN++

4. Development Part III (July 01 - July 15):
Scripts and modules related to INSTALL and the INSTALL file
itself.

5. Packaging (July 15 - August 5):
Database Manager and a fresh Upgrade file and related
modules.

6. Testing and Wrap-Up (August 5 - August 21):
Thoroughly test every aspect of the finished package. This
phase will
also include the development of non-code deliverables.

~~~
Bio
~~~
I am a third-year undergraduate at the Malaviya National
Institute of
Technology, Jaipur, India. I am pursuing my B.Tech. in
Computer
Engineering at the institute. I have been passionate about
computers
since my childhood and have been a free software advocate
for around 3
years now.

I have contributed to several opensource projects, the most
prominent
among them have been Gentoo, Apertium and  Mozart. These
projects have
helped me clear most of my concepts in C and Perl. I also
am
interested in Natural Language Processing, where I have
mostly used
perl for the purpose of Regular Grammars. These I believe
are the
essential requirements for this projects. I have also
created a small
content management system and an Online Judge(code Testing
Platform)
with perl.

Finally, I would like to express my deep commitment to this
project.
You can find more details about me and the projects that I
am
currently involved in, at my
website. Please don't hesitate to contact me if any part of
this
proposal is not clear to you.

Thank you for considering this proposal, and for your time!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
My CV     : http://pranava.rsp
an.in/resume.pdf
My Website: http://pranava.rspan.in/

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Cheers

Pranava

On Sat, Mar 29, 2008 at 10:26 PM, PRANAV
<pranava.madhyasthagmail.com> wrote:
>
> Hi,
>
>  My second iteration:
>
>  ~~~~~~~~~~~~~~~~~~
>  Pranava Swaroop S
>  pmadhyasthaacm.org
>  ~~~~~~~~~~~~~~~~~~
>
>  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  REJUVENATING THE INSTALLER FOR BRICOLAGE
>  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  Greetings!
>
>  I quote from "Bricolage" website:
>
>  "Bricolage, an open-source enterprise-class
content management system,
>  greatly simplifies the complex tasks of creating,
managing, and
>  publishing the vast libraries of content essential to
any
>  organization."
>
>  I wish to take the improvement of the installer and
the development of
>  the modules associated with Bricolage as a part of the
Google's Summer
>  of Code initiative. This project will help resolve
most of the
>  installer based problems of Bricolage.
>  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  Benefits to the Bricolage Community
>  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  This project would simplify the whole process of
installation and
>  would gel beautifully to the afore mentioned quote.
This project will
>  also enhance the usage scope of Bricolage
considerably.
>
>  ~~~~~~~~~~~~
>  Deliverables
>  ~~~~~~~~~~~~
>  1. Creation of a perl build file(does the job of
configuring and
>  building Bricolage) with sub-modules for
'OS-Specific'
>  installation(with OS-specific hints in case the
installation fails)

Does that means you will bid good bye to bricolage.conf ?
>
>  2. Creation of a robust-user-friendly INSTALL
file(which does hassle
>  free 'download and install' process when a module is
not found)

 I think you should rename this file to something else.
INSTALL file
normally contains installation instructions on how to
install. You may
call it cpan-install.pl to avoid confusion.

>
>  3. A script to manage the database back-end during the
process of
>  installation(this script would also support
command-line arguments)

 Ok, How will a user specify things like, database user and
password ?
Do you plan to make a conf file (using standard ini format
?).

>
>  4. A separate upgrade script(this script would be
re-written in order
>  to simplify the process of updation).
>
>  5. Polishing the package to smoothen the process of
installation,
>  which should guarantee trouble free
installation/up-dation to the
>  user.
>
>  Non-Code deliverables will include documentation for
all the scripts
>  and modules mentioned above.

 Again, I do not see any options to specify installation
specific
configuration ? Hint:
1) Command line input
2) conf file
3) please dont make a xml file for configuration

<snip>
>
>  Suggestions are welcome!
>  ~~~~~~~~~~~~~~~~
>  Project Schedule
>  ~~~~~~~~~~~~~~~~
>  The project is planned to be split across 6 major
Phases:
>
>  1. Analysis (May 26 - May 31)(I would be happy if I
could start early):
>  This phase involves interaction with the mentor and
the key people
>  involved in similar projects  in order to exactly
understand the
>  requirements.
>
>  2. Development Part I (June 1 - June 15):
>  This phase will involve the creation of the afore
mentioned build file.
>
>  3. Development Part II (June 16 - June 30):
>  Re-incarnation of cpan.pl and modules which would work
with CPAN++
>
>  4. Development Part III (July 01 - July 15):
>  Scripts and modules related to INSTALL and the INSTALL
file itself.
>
>  5. Packaging (July 15 - August 5):
>  Database Manager and a fresh Upgrade file and related
modules.
>
>  6. Testing and Wrap-Up (August 5 - August 21):
>  Thoroughly test every aspect of the finished package.
This phase will
>  also include the development of non-code
deliverables.
>

 You need to specify what will be covered till mid-term
evaluation.
Rest seems okay to me.

regards
VK

-- 
The hidden harmony is better than the obvious!!

On Sun, Mar 30, 2008 at 03:56:23AM +0530, PRANAV wrote:
> Hi,
> 
> My second iteration:
> 
> ~~~~~~~~~~~~~~~~~~
> Pranava Swaroop S
> pmadhyasthaacm.org
> ~~~~~~~~~~~~~~~~~~
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> REJUVENATING THE INSTALLER FOR BRICOLAGE
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Greetings!
> 
> I quote from "Bricolage" website:
> 
> "Bricolage, an open-source enterprise-class
content management system,
> greatly simplifies the complex tasks of creating,
managing, and
> publishing the vast libraries of content essential to
any
> organization."
> 
> I wish to take the improvement of the installer and the
development of
> the modules associated with Bricolage as a part of the
Google's Summer
> of Code initiative. This project will help resolve most
of the
> installer based problems of Bricolage.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Benefits to the Bricolage Community
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> This project would simplify the whole process of
installation and
> would gel beautifully to the afore mentioned quote.
This project will
> also enhance the usage scope of Bricolage
considerably.
> 
> ~~~~~~~~~~~~
> Deliverables
> ~~~~~~~~~~~~
> 1. Creation of a perl build file(does the job of
configuring and
> building Bricolage) with sub-modules for 'OS-Specific'
> installation(with OS-specific hints in case the
installation fails)
> 
> 2. Creation of a robust-user-friendly INSTALL
file(which does hassle
> free 'download and install' process when a module is
not found)
> 
> 3. A script to manage the database back-end during the
process of
> installation(this script would also support
command-line arguments)
> 
> 4. A separate upgrade script(this script would be
re-written in order
> to simplify the process of updation).

The word "updation" is new to me... I think the
phrase you really want here is "simplify the update
process", or "simplify the process of
updating".

> 5. Polishing the package to smoothen the process of
installation,

"smooth the process"

> which should guarantee trouble free
installation/up-dation to the
> user.
> 
> Non-Code deliverables will include documentation for
all the scripts
> and modules mentioned above.
> 
> ~~~~~~~~~~~~~~~
> Project Details
> ~~~~~~~~~~~~~~~
> The main objective of the project is to ease out the
process of
> installation and to make the installer more user
friendly, at the same
> time, making the installer noise free for the
developers too, which
> should result in hassle free updation and maintenance.
> 
> The first part of the project is to make a perl-build
scripts using
> CPAN based modules. This would contain Module::Build,
Locale::Maketext
> for the process of building and App::Info for the
dependency
> detection. The main aim here is to eliminate the
standard unix
> makefiles and configuration files. Also David's
FSA::Rules module will
> be used to handle decision trees. There would be
verbose comments if
> at all there is an error. These should help the user to
carve the
> right path.
> 
> At present, the Bricolage installer seems to have
problems in
> automating many installations of important CPAN
modules. The cpan.pl
> file would be rewritten to resolve such issues. Also, a
new support
> for CPAN++ would be added, which would require
additional modules to
> be written.
> 
> The INSTALL file with default options would be created.
This would
> also support custom options which could be explicitly
stated from the
> command line, when INSTALL is being called.
> 
> Creation of a database manager(to manage DB during the
install). This
> database manager manages the back-end of the DB and
also creates the
> databases. This script will again provide custom
command line options
> which the user can provide, thereby, easing out the DB
related
> process.
> 
> The upgrade script would be modified and would be made
more verbose.
> The objective here is to give user the flexibility of
the upgrade and
> ease of backup and restore.
> 
> Finally, other scripts which are used during the
process of
> installation would be optimized.
> 
> Suggestions are welcome!
> ~~~~~~~~~~~~~~~~
> Project Schedule
> ~~~~~~~~~~~~~~~~
> The project is planned to be split across 6 major
Phases:
> 
> 1. Analysis (May 26 - May 31)(I would be happy if I
could start early):
> This phase involves interaction with the mentor and the
key people
> involved in similar projects  in order to exactly
understand the
> requirements.
> 
> 2. Development Part I (June 1 - June 15):
> This phase will involve the creation of the afore
mentioned build file.
> 
> 3. Development Part II (June 16 - June 30):
> Re-incarnation of cpan.pl and modules which would work
with CPAN++
> 
> 4. Development Part III (July 01 - July 15):
> Scripts and modules related to INSTALL and the INSTALL
file itself.
> 
> 5. Packaging (July 15 - August 5):
> Database Manager and a fresh Upgrade file and related
modules.
> 
> 6. Testing and Wrap-Up (August 5 - August 21):
> Thoroughly test every aspect of the finished package.
This phase will
> also include the development of non-code deliverables.

How are you proposing the testing is to be done -- will the
test harness actually be part of the deliverables?

> ~~~
> Bio
> ~~~
> I am a third-year undergraduate at the Malaviya
National Institute of
> Technology, Jaipur, India. I am pursuing my B.Tech. in
Computer
> Engineering at the institute. I have been passionate
about computers
> since my childhood and have been a free software
advocate for around 3
> years now.
> 
> I have contributed to several opensource projects, the
most prominent
> among them have been Gentoo, Apertium and  Mozart.
These projects have
> helped me clear most of my concepts in C and Perl. I
also am
> interested in Natural Language Processing, where I have
mostly used
> perl for the purpose of Regular Grammars. These I
believe are the
> essential requirements for this projects. I have also
created a small
> content management system and an Online Judge(code
Testing Platform)
> with perl.
> 
> Finally, I would like to express my deep commitment to
this project.
> You can find more details about me and the projects
that I am
> currently involved in, at my
> website. Please don't hesitate to contact me if any
part of this
> proposal is not clear to you.
> 
> Thank you for considering this proposal, and for your
time!
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> My CV     : http://pranava.rsp
an.in/resume.pdf
> My Website: http://pranava.rspan.in/

> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> Cheers
> 
> Pranava

-- 

Brad Harder,
Method Digital Logic
http://www.methodlogic.net

First of all thanks for the lightening reply and great
suggestions
vivek and bharder.

>Does that means you will bid good bye to bricolage.conf
?
That may not be true as bricolage.conf is more to do with
apache, so
this may  stay behind.

> I think you should rename this file to something else.
INSTALL file
>normally contains installation instructions on how to
install. You may
>call it cpan-install.pl to avoid confusion.
Affirmative, changed to cpan-install.pl.


> Ok, How will a user specify things like, database user
and password ?
>Do you plan to make a conf file (using standard ini
format ?).
Voila! yeah, I was planning to do that. Made the changes.

> You need to specify what will be covered till mid-term
evaluation.
Midterm evaluations <---- added

>The word "updation" is new to me... I think
the phrase you really
want here is >"simplify the update process", or
"simplify the process
of updating".
Accepted

>"smooth the process"
As per wordnet smoothen is defined and it means to make it
more
smooth. I think it should gel together.

>How are you proposing the testing is to be done -- will
the test
harness actually be >part of the deliverables?
I would complete the whole process of coding and then commit
the
package <== it would be public then. After which there
will be a
continuous process of testing not only by me and the
developers but
users. And based on the bugs the errors will be corrected.
Note that
this is a continuous process.
But I don't exactly know whether this should be included in
the deliverables.

Please suggest me if I am going wrong again!

Best
Pranava Swaroop S

>
>  >How are you proposing the testing is to be done --
will the test
>  harness actually be >part of the deliverables?
>  I would complete the whole process of coding and then
commit the
>  package <== it would be public then. After which
there will be a

 Please dont tell us that you will commit an untested
patch.

>  continuous process of testing not only by me and the
developers but
>  users. And based on the bugs the errors will be
corrected. Note that
>  this is a continuous process.
>  But I don't exactly know whether this should be
included in the deliverables.
>

 In short, atleast tell us how you plan to test that new
installer has
installed stuff properly, without breaking anything in the
base
system.
 You need to figure out what all will be tested and how it
will be
tested. We are not looking at exact test cases but a
description on
how you plan to test the new installer.

regards
VK


-- 
The hidden harmony is better than the obvious!!

On Mar 29, 2008, at 16:09, Pranav wrote:

>> Does that means you will bid good bye to
bricolage.conf ?
> That may not be true as bricolage.conf is more to do
with apache, so
> this may  stay behind.

Confirmed. bricolage.conf is runtime configuration, not
installation  
configuration. The latter does inform the former, however.
Which means  
that some configuration data you collect during installation
needs to  
be written to bricolage.conf. There is an existing script
that does  
this.

>> Ok, How will a user specify things like, database
user and password ?
>> Do you plan to make a conf file (using standard ini
format ?).
> Voila! yeah, I was planning to do that. Made the
changes.

Where?

>> You need to specify what will be covered till
mid-term evaluation.
> Midterm evaluations <---- added

Will you be resubmitting something?

>> "smooth the process"
> As per wordnet smoothen is defined and it means to make
it more
> smooth. I think it should gel together.

"Lube" is the word you're looking for. (NOT
REALLY.)

>> How are you proposing the testing is to be done --
will the test
> harness actually be >part of the deliverables?
> I would complete the whole process of coding and then
commit the
> package <== it would be public then. After which
there will be a
> continuous process of testing not only by me and the
developers but
> users. And based on the bugs the errors will be
corrected. Note that
> this is a continuous process.

Ideally there would be a test suite for the installer. This
is the  
nice thing about FSA::Rules: you can write tests for the
rules.

> But I don't exactly know whether this should be
included in the  
> deliverables.

Tests should always be a part of the deliverables.

Best,

David

On Mar 29, 2008, at 10:15 PM, David E. Wheeler wrote:

> On Mar 29, 2008, at 16:09, Pranav wrote:
>
>>> Does that means you will bid good bye to
bricolage.conf ?
>> That may not be true as bricolage.conf is more to
do with apache, so
>> this may  stay behind.
>
> Confirmed. bricolage.conf is runtime configuration, not
installation  
> configuration. The latter does inform the former,
however. Which  
> means that some configuration data you collect during
installation  
> needs to be written to bricolage.conf. There is an
existing script  
> that does this.

As far as installation options go, see also inst/defaults/*,
which can  
set defaults for all of the installation questions, allowing
for a  
totally silent installation on Gentoo and FreeBSD. That's
necessary to  
cater to all of the various distributions' directory
structures.

--
Marshall

On Sun, Mar 30, 2008 at 01:25:51AM -0400, Marshall Roch
wrote:
> On Mar 29, 2008, at 10:15 PM, David E. Wheeler wrote:
> 
> >On Mar 29, 2008, at 16:09, Pranav wrote:
> >
> >>>Does that means you will bid good bye to
bricolage.conf ?
> >>That may not be true as bricolage.conf is more
to do with apache, so
> >>this may  stay behind.
> >
> >Confirmed. bricolage.conf is runtime configuration,
not installation  
> >configuration. The latter does inform the former,
however. Which  
> >means that some configuration data you collect
during installation  
> >needs to be written to bricolage.conf. There is an
existing script  
> >that does this.
> 
> As far as installation options go, see also
inst/defaults/*, which can  
> set defaults for all of the installation questions,
allowing for a  
> totally silent installation on Gentoo and FreeBSD.
That's necessary to  
> cater to all of the various distributions' directory
structures.

Nice -- good tip, Marshall...

> --
> Marshall

-- 

Brad Harder,
Method Digital Logic
http://www.methodlogic.net