[TriLUG] rpm database question

[Lisa Lorenzin]

for folks running redhat, how do you reconcile wanting to compile your own
versions of things with wanting to keep the rpm database up to date?

for example, i'm seriously considering installing the latest version of
sendmail on my new RH7.2 box.  there's not an rpm for it yet, and even if
there was, i'd like to make some customizations to it (nothing fancy -
just cosmetic).  at that point, what my rpm database knows about will be
out of sync with what my box has, which will screw up my automatic updates
via rhup and confuse me mightily when i go to do something else with
sendmail in 6 months, having totally forgotten i did this.  (okay, with my
memory, make that 2 months.)

so, is there any way around this?  do i have to just choose between
compiling my own versions and having rpm reflect reality, or can i have my
cake and eat it too?

one option would seem to be compiling it, building my own rpm from what i
compile, removing what i compiled, and installing it via my new rpm - but
a) that seems like going around my rear to get to my elbow, and b) i've
never built an rpm before, so i'm not sure i'd be able to trust what came
out of that process.

any clues will be greatly appreciated!

						lisa

-- 
lisa lorenzin   |   lorenzin at 1000plus.com   |   http://www.1000plus.com/lisa/
# find / -user your -name base -print0 | xargs -0 chown us