Like a few others posting here recently, I'd really like to use s3ql
on CentOS 6.  Amongst the list of requirements is the upgrade of
sqlite from 3.6 to 3.7.  This one is a little troubling, since sqlite
is pretty intrinsic to CentOS (RHEL etc.) - used by yum, for example.
Changing the version of sqlite from the CentOS 6-supplied 3.6, to a
3rd party repo-provided 3.7, means your OS technically stops being
CentOS.  This may be something I can live with on a home system, but I
cannot recommend this to anyone at $work.  We have enough trouble with
other things like php from the atomic repo, since our customers don't
often understand the rationale behind repos like atomic (latest!!
yeah! oops, why has stuff stopped working?), vs the sensible,
conservative CentOS/RHEL/EPEL repos (major version stays unchanged,
all apps keep working, backfixing of bugs, sleep easy at night...!).

Nikolaus, please don't take this as a complaint, since you obviously
have good reasons for the s3ql code needing sqlite 3.7, as is your
right :), but I would love to know if this is a 'hard' requirement, or
would there be any way to use s3ql with sqlite left at 3.6?

Many thanks      Andy

-- 
You received this message because you are subscribed to the Google Groups 
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to