Re: db3 and beecrypt in RPM source tree

[<greg_mu yahoo com>]

Hi Jeff,

Thanks for the insights. I probably came up with the
bad example in my
original post.  I think that I can fix configure
scripts and it's not a
problem.  My concern is related to what I see as
bundling multiple
products (RPM, db3, beecrypt, etc) into a single
deployment unit.

I see two scenarios here: initial RPM build and the
RPM build under the
RPM tool itself (more typical scenario).

In the first case, if you don't want to track
compatibility with the
older versions, it's OK to say in the INSTALL notes
that the build requires
db3 package equal to some specific tarball version. 
This is quite typical
and the users won't have any issues with that.

In the second scenario, I don't see why you can't just
use the RPM dependency
checks and let the other RPM packages (db3, beecrypt,
etc.) have their own lifecycle.
After all this is what RPM was made for 8-). Also
please cosider that you may sooner
or later cause a collision with the packages RPM uses
internally when those packages
will be installed on the system independently.  

I still do not see any benefits in bundling the
tarballs together. After all,
If you are not introducing some private changes to the
"third party" products,
why keep them together? 

Thanks,
Greg

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com