rpm expectations/conventions

[marks <marks adax com>]

Hi,

I'm fairly new to rpm and have a few questions regarding the expectations 
of an rpm end-user with regards to installed/generated files.

When installing the rpm, is it expected that every file installed or 
generated when running "rpm -i" be owned (rpm -qf) by the package?

If so, how do I get files that are built on the fly by the scriptlets in
the rpm to show in the rpm database as owned by the package (rpm -qf}?

If I put these files in the %files section rpmbuild fails as the files 
don't exist yet.  I suppose I could use touch to create placeholder files 
then overwrite them but would rather follow the proper conventions.

Also, the rpm I am developing will hopefully support all our currently
supported 2.4 and 2.6 kernels regardless of linux vendor (redhat, SuSE,
MontaVista, etc.).  What mechanism do people use to determine where to
install an init.d startup script (/etc/init.d, /etc/rc.d/init.d, etc.)?  

Each linux vendor seems to have a different location for the init.d
directory.  I do know that many vendors include a symlinked /etc/init.d
directory that points to their actual init.d directory but I'd rather not
use that as a crutch.  Then of course I have to deal with all the 
different vendor utilities for managing init.d scripts (chkconfig, 
insserv, update-init.d, etc.).

Any tricks tips in this area?

-- 
Thanks,

Mark