Forwarded Conversation
Subject: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE
------------------------
From: Vladimir Glazounov <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Thu, Apr 12, 2007 at 10:46 PM
IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT
===========================================================
Hi all,
the ongoing SRC680 m209 build brings important change to our build
environment. Since that milestone hedabu procedure will not work.
To make it happen, many headers are moved to module's include specific
folder, ie $MODULE/inc/$MODULE, where $MODULE is the name of a
module.
The new files in $MODULE/inc/$MODULE folder correspond to the last
revision of their prototypes, ie m208.
IMPORTANT(!!) for all cws owners: if your on the SRC680 based CWS has
changes in headers - please resync the CWS to the m209(or later).
Achtung(!) - if header was moved in m209 - the changes will not be
reflected in new reincarnation of the file, so you have to make your
changes in the new file MANUALLY.
Best regards,
Vladimir
=================================================================
Sun Microsystems GmbH Vladimir Glazunov
Nagelsweg 55 Development - Release Engineer
20097 Hamburg Phone: (+49 40) 23646 861
Germany Fax: (+49 40) 23646 608
http://www.sun.de mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------
From: Bjoern Milcke <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Fri, Apr 13, 2007 at 12:19 AM
Hi Vladimir,
IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT
===========================================================
Hi all,
the ongoing SRC680 m209 build brings important change to our build
environment. Since that milestone hedabu procedure will not work.
To make it happen, many headers are moved to module's include specific
folder, ie $MODULE/inc/$MODULE, where $MODULE is the name of a
module.
The new files in $MODULE/inc/$MODULE folder correspond to the last
revision of their prototypes, ie m208.
IMPORTANT(!!) for all cws owners: if your on the SRC680 based CWS has
changes in headers - please resync the CWS to the m209(or later).
Achtung(!) - if header was moved in m209 - the changes will not be
reflected in new reincarnation of the file, so you have to make your
changes in the new file MANUALLY.
What changes? What do we have to do? What did the CWS fix? In Issue
72503 there is exactly *NO* description of what has been done.
Was the only thing the move of some headers? Delivered headers only?
Do we have to do any changes in CWS chart2mst3, where we added a new
module with new headers?
-Bjoern
[Quoted text hidden]
--------
From: Rüdiger Timm <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Fri, Apr 13, 2007 at 1:11 AM
Bjoern Milcke wrote:
Hi Vladimir,
IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT
===========================================================
Hi all,
the ongoing SRC680 m209 build brings important change to our build
environment. Since that milestone hedabu procedure will not work.
To make it happen, many headers are moved to module's include specific
folder, ie $MODULE/inc/$MODULE, where $MODULE is the name of a
module.
The new files in $MODULE/inc/$MODULE folder correspond to the last
revision of their prototypes, ie m208.
IMPORTANT(!!) for all cws owners: if your on the SRC680 based CWS has
changes in headers - please resync the CWS to the m209(or later).
Achtung(!) - if header was moved in m209 - the changes will not be
reflected in new reincarnation of the file, so you have to make your
changes in the new file MANUALLY.
What changes? What do we have to do? What did the CWS fix? In Issue
72503 there is exactly *NO* description of what has been done.
Your changes.
That CWS completely removed the 'hedabu' action from deliver.
Was the only thing the move of some headers? Delivered headers only?
Moving of delivered headers from f.e. svx/inc into svx/inv/svx. Adapting
includes accordingly. Adapting d.lst files.
Do we have to do any changes in CWS chart2mst3, where we added a new
module with new headers?
-Bjoern
I more detail:
If you did not touch headers, no action is required.
If you changed existing headers or introduced new ones, check in
prj/d.lst, whether those headers are subject to 'headbu' action. If they
are not: no action required.
If your header was 'hedabu'ed it most probably got removed by Vladimir
and moved to an new location, as stated above. Moving files is not
really supported by cvs. Therefore you have to check your changes, i.e.
cvs diff -r <CWS_ANCHOR> -r <cws_branch> <file> and apply those changes
to the moved header. If you introduced a new one subject to hedabu, move
it to the appropriate directory and adapt include directives (i.e. for
the above svx example change #include "myheader.hxx" into #include
"svx/myheader.h" where needed). Finally, adapt d.lst.
Rüdiger
[Quoted text hidden]
--------
From: Bjoern Milcke <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Fri, Apr 13, 2007 at 1:54 AM
Hi Rüdiger,
Bjoern Milcke wrote:
Hi Vladimir,
IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT
===========================================================
[...]
Do we have to do any changes in CWS chart2mst3, where we added a new
module with new headers?
-Bjoern
I more detail:
If you did not touch headers, no action is required.
If you changed existing headers or introduced new ones, check in
prj/d.lst, whether those headers are subject to 'headbu' action. If they
are not: no action required.
If your header was 'hedabu'ed it most probably got removed by Vladimir
and moved to an new location, as stated above. Moving files is not
really supported by cvs. Therefore you have to check your changes, i.e.
cvs diff -r <CWS_ANCHOR> -r <cws_branch> <file> and apply those changes
to the moved header. If you introduced a new one subject to hedabu, move
it to the appropriate directory and adapt include directives (i.e. for
the above svx example change #include "myheader.hxx" into #include
"svx/myheader.h" where needed). Finally, adapt d.lst.
Thanks a lot. That clarified it!
-Bjoern
[Quoted text hidden]
--------
From: Vladimir Glazounov <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Fri, Apr 13, 2007 at 7:04 PM
Actually, fist do resync, "deliver -delete", update sources, replicate
changes in headers, if needed- move headers+correct "#includes", build
sources. You will see quite quickly if you did something wrong, what to
to will be obvious...
Vladimir
Was the only thing the move of some headers? Delivered headers only?
Moving of delivered headers from f.e. svx/inc into svx/inv/svx. Adapting
includes accordingly. Adapting d.lst files.
Do we have to do any changes in CWS chart2mst3, where we added a new
module with new headers?
-Bjoern
I more detail:
If you did not touch headers, no action is required.
If you changed existing headers or introduced new ones, check in
prj/d.lst, whether those headers are subject to 'headbu' action. If they
are not: no action required.
If your header was 'hedabu'ed it most probably got removed by Vladimir
and moved to an new location, as stated above. Moving files is not
really supported by cvs. Therefore you have to check your changes, i.e.
cvs diff -r <CWS_ANCHOR> -r <cws_branch> <file> and apply those changes
to the moved header. If you introduced a new one subject to hedabu, move
it to the appropriate directory and adapt include directives (i.e. for
the above svx example change #include "myheader.hxx" into #include
"svx/myheader.h" where needed). Finally, adapt d.lst.
<svx/myheader.h>
Rüdiger
[Quoted text hidden]
--------
From: Mathias Bauer <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Fri, Apr 13, 2007 at 10:46 PM
Rüdiger Timm wrote:
If you did not touch headers, no action is required.
If you changed existing headers or introduced new ones, check in
prj/d.lst, whether those headers are subject to 'headbu' action. If they
are not: no action required.
If your header was 'hedabu'ed it most probably got removed by Vladimir
and moved to an new location, as stated above. Moving files is not
really supported by cvs. Therefore you have to check your changes, i.e.
cvs diff -r <CWS_ANCHOR> -r <cws_branch> <file> and apply those changes
to the moved header. If you introduced a new one subject to hedabu, move
it to the appropriate directory and adapt include directives (i.e. for
the above svx example change #include "myheader.hxx" into #include
"svx/myheader.h" where needed). Finally, adapt d.lst.
In case you wonder how you can find out which header files you might
have changed: use cwsanalyze to find all changes in your CWS. This is
the best way to avoid problems, it is known that not all possible
combinations of header changes cause errors or alerts in the resync
process. So some conflicts might remain unnoticed while doing the resync
without a prior analyse step.
Ciao,
Mathias
--
Mathias Bauer (mba) - Project Lead OpenOffice.org Writer
OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
Please don't reply to "[EMAIL PROTECTED]".
I use it for the OOo lists and only rarely read other mails sent to it.
[Quoted text hidden]
--------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
