"Eric Pugh" <[EMAIL PROTECTED]> writes:
>Henning,
>I wanted to start documenting the changes for 2.4, and I thought I might do
>that through adding antoher flavor to META. However, some things are at the
>common/ directory that aren't appropriate for 2.4.
>How would I handle providing a turbine-2.4 TR.props file for example?
Just put it into flavor/turbine-2.4/conf. If META sees a config file
in a flavor subdirectory, it should skip the file from
flavor/common. This is how it is intended to work, if it does not, it
is a bug and I will fix it.
It gets a bit trickier if there is a file in common which you _don't_
want in your flavor. Then you must copy this file into all other
flavors and remove it from common.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
"Fighting for one's political stand is an honorable action, but re-
fusing to acknowledge that there might be weaknesses in one's
position - in order to identify them so that they can be remedied -
is a large enough problem with the Open Source movement that it
deserves to be on this list of the top five problems."
-- Michelle Levesque, "Fundamental Issues with
Open Source Software Development"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
