Hi, I do agree with you, but as far as i remember EPEL provides packages that does not exist in RHEL5 official upstream. we are using sqlite 3.4.2 and rpm and all sqlite aware apps are working perfectly :-)
if you want to keep the official sqlite and install the 3.4.2 version it would need more work in both sides. for sqlite you will need to install in separate directories. create binary with version .... for opendnssec you will need to link it to the sqlite version you have build. .... i see two options: 1°) chroot opendnssec and all of his dependencies 2°) static link between opendnssec and sqlite 3.4.2 Rachid On Tue, Apr 13, 2010 at 10:08 AM, Ville Mattila <[email protected]> wrote: > Hi, > > > On Mon, 12 Apr 2010, Rachid Zarouali wrote: > > as promised find attached specs file i've tweaked or made :-) >> > > Thanks! Unfortunately the problem of opendnssec depending on Sqlite > v3.4.2+ still would need another solution, because it seems your sqlite > package replaces the RHEL/CentOS 5 official sqlite installation. > > I'm sorry but this is exactly what I'm hoping we could avoid, that is, not > to force package users "void warranty" of their RHEL/CentOS installation > by replacing system software (sqlite is required by e.g. RPM tool itself). > > To attract more RHEL/CentOS 5 users to use OpenDNSSEC I think it would > be good to have the packages distributed via EPEL where the policy on > replacing official parts is strict: > > EPEL FAQ [1]: > "Does EPEL replace packages provided within Red Hat Enterprise Linux > or layered products? > > No. EPEL is purely a complimentary repository that provide add-on > packages." > > [1] > http://fedoraproject.org/wiki/EPEL/FAQ#Does_EPEL_replace_packages_provided_within_Red_Hat_Enterprise_Linux_or_layered_products.3F > > > Ville >
_______________________________________________ Opendnssec-user mailing list [email protected] https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
