Issue 90651 - perl script for applying patches ...
Summary: perl script for applying patches ...
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: 680m240
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2008-06-12 11:00 UTC by mmeeks
Modified: 2013-03-11 15:02 UTC (History)
3 users (show)

See Also:
Issue Type: PATCH
Latest Confirmation in: ---
Developer Difficulty: ---

apply perl script (30.49 KB, text/plain)
2008-06-12 11:00 UTC, mmeeks
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description mmeeks 2008-06-12 11:00:10 UTC
I attach the perl script we use for applying patches to ooo-build: it might be
useful to have this included up-stream with a generic patching mechanism; the
apply file syntax is fairly self explanatory.

If this goes up-stream, it will require more work, to allow ooo-build to
override patches, and (I think) layer a smaller apply file on top of this - but
that shouldn't be too much work.

Urgh - I guess we would also want a way to disable up-stream applied patches
(out of our control) too. Anyhow, the apply file syntax looks a little like this:


# -------- Functional sub-sets --------
Common : PreprocessPatches, BuildBits, TemporaryHacks, FixesNotForUpstream, ...

[ TemporaryHacks ]
# build our stuff
# FIXME: should be in the respective patches
buildfix-no-UPD-in-library-names.diff, jholesov

Comment 1 mmeeks 2008-06-12 11:00:35 UTC
Created attachment 54423 [details]
apply perl script
Comment 2 Rob Weir 2013-03-11 15:02:54 UTC
I'm adding this comment to all open issues with Issue Type == PATCH.  We have 220 such issues, many of them quite old.  I apologize for that.  

We need your help in prioritizing which patches should be integrated into our next release, Apache OpenOffice 4.0.

If you have submitted a patch and think it is applicable for AOO 4.0, please respond with a comment to let us know.

On the other hand, if the patch is no longer relevant, please let us know that as well.

If you have any general questions or want to discuss this further, please send a note to our dev mailing list: