![]() Create an empty NeoOffice-3.4.1 directory outside of the workspace.The following steps are the steps that I used to create my backup copy: Note that by creating the certs.mk file, signing of the installer and the application will be enabled.Ĭreate backup copy of releasable Intel binaries and upload them to staging server. Invoke cp certs.mk make all to create the releasable installer and language packs.This will force the installer to rebuild all of the NeoOffice custom code without causing any of the or ooo-build code to be rebuilt. If any differences appear, the previous task (tagging of the workspace) has not been done properly and it needs to done properly before you can proceed with this task. Do a cvs diff -rNeoOffice-3_4_1 and verify that there are no differences for any of the files.If any such markings appear, the previous task (tagging of the workspace) has not been done properly and it needs to done properly before you can proceed with this task. Do a cvs update -rNeoOffice-3_3_branch -d and verify that none of the files are marked as updated, patched, modified, or have conflicts.Note: the following steps are overkill, but they ensure that all recent changes to the NeoOffice custom code has been built: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |