[Opendnssec-develop] Dependencies & stock distributions

[Rickard Bellgrim]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

> One worry for me is that a given HSM will run on a particular platform,
> RHEL5 being a common example, and won't mix with all the dependencies
> needed to run OpenDNSSEC.  The more software versions are limited to
> one particular version, the higher the chances of disturbing things in
> the versioning arena.

Let's face it. When developing new software, you want to use up-to-date libraries so that you do not stand still but evolve. The standards have not been here for years. We must thus use updated libraries.

> All these things can of course be solved by installing dependencies in
> other prefixes, but that makes OpenDNSSEC deviate (strongly) from the
> push button ideal.  Acute knowledge of the version ranges that work
> would be really useful, as well as constraining ourselves in the
> software facilities that we rely upon.

No (advanced) software are push the button until they are packaged. Rome was not built in one day.

> Ruby is one factor that makes OpenDNSSEC deviate from the ideal of a
> pushbutton/turnkey solution.  Many users may find it to be a new
> language and a new installation skillset.

(./configure --disable-auditor)

// Rickard

-----BEGIN PGP SIGNATURE-----
Version: 9.8.3 (Build 4028)
Charset: utf-8

wsBVAwUBSyeyn+CjgaNTdVjaAQg+mQgAjFUanUsix+SERkkf0jbgwAknfSHdkN5T
Po3E8FnLjH9K7xOojlCPU9ifyFYVyy7Ydxdr1BkvDq5vsgX21dEDv/P3y8qCy3Wl
AL2vgmqz5PkPisGTdDhWf+1MjJtxqT6gqAS4OWSgnWvEubydgMq6LD4VmGaZgznb
kNJhM3Q13fdgsiKXadJu5KdpSF0hKJ6ZGXjGcHHgI5AUFCpY0+C3/ENS6WB2jlrp
8ZkcWCDKA38qLx5C5ShkDL+dNWTOjszKqV9piV1cCpIeF/YQw2TNsvESK95r4fLA
2MyrcmluIHPiRTQenMoPulOx8rKS3BKo6y5sm3BjnLIEIlRijl8ZMA==
=NKvA
-----END PGP SIGNATURE-----


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20091215/05bf5316/attachment.htm>