GPL bundling question [off topic]

A question for those who have sold software that uses / calls GPL'ed software. Assume I have a REBOL program (an executable produced by the SDK) that has a reporting function which creates an OpenOffice document (written entirely in REBOL for the sake of the argument). Given that someone who buys my software is unlikely to have OpenOffice installed (on Windows at least) and that OpenOffice is a "typical" GPL program, what are my options for bundling OpenOffice on the same CD? a) Can I place the 63.5MB OpenOffice zip file on my product CD in the first place? b) If so, can my installation program unzip it and then run the OO installer? c) If this is allowed, can I place the uncompressed contents [without alteration] of the OO zip file on my CD? (so my installation program can call the OO setup.exe file without having to unzip the distribution) d) What reasonable and responsible steps should be taken to give credit where credit is due? Acknowledge my product's use of OO in the documentation and / or installation process? Ensure my reporting function has a hyperlink to the OO website? Make sure the OO logo appears alongside the REBOL logo in an about / copyright dialog? I just want to know what my obligations (both legal and moral) are if I bundle GPL binaries that my [closed source] software makes use of. Regards, Ashley