Hi Giuseppe,
Giuseppe Castagno wrote:
Hi all,
I have a question about the right procedure to follow to add
a new module (sorry for the lengthy message).
The module I'm adding is a follow up to issue 81093 [1].
I read the notes on the wiki [2] to have an idea on how to proceed.
So far I've created the directory structure on head [3] and have added
some of the files there.
The new module alias has been created.
The steps I intend to follow are:
1. Finishing committing in HEAD all the new module files (see [4] for
a module description), through the alias.
2. On the new cws I'm going to create, I'll add only the OOo module that
needs to be adapted (vcl) and made it dependent to the new one.
3. I'll then add a note on EIS about the new module to be added while
integrating.
4. Go on with the usual work, committing vcl changes to CWS and the new
module changes to HEAD.
My questions are:
- are these steps the correct ones?
Yes, that's correct.
- is there a way to have the new CWS built on buildbot?
Unfortunately not.
- the new module (icc, [4], in external/icc) should be added to the CWS
or should I continue to commit the code in that module alone to HEAD?
New modules not yet in the master workspace cannot be added to a CWS.
You have to continue working head.
Thank you very much for asking and taking care not to break something.
BTW, if you feel sad not beeing able to build new modules on buildbots
and tinderboxes you are not alone :-(
Rüdiger
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
