Hi guys,
----- Original Message -----
> On 11/30/2012 03:18 AM, Nathan Scott wrote:
> > ----- Original Message -----
> >> ...
> >> So, approach used so far is to add the sort of tests we have now
> >> (PCP version based) as an initial "will this compile at all"
> >> check,
> >> then a subsequent "dynamic" check is done via a call into a libpcp
> >> routine that was added at the time of the initial feature commit.
> >>
> >> There's pros and cons. NSS doesn't actually have a routine like
> >> this and we'd have to add something. Need to think further on the
> >> best option I think - maybe adding in a feature-test interface to
> >> libpcp (analogous to sysconf(3), but less int-based) and also a
> >> helper tool (something like getconf(1), for QA)?
> >>
> >> Another option would be to use the pkg-config tool I guess. Or we
> >> continue on the query-interface-per-feature path, which works too.
> > Attached patch is an initial pass (untested) at approach #1 for
> > your
> > consideration & amusement. I came across the existing pmconfig(1)
> > &
> > made this fit into that tool, with similar APIs.
> >
> > Thoughts?
> >
> I like the idea of being able to query the library regarding its
> features/capabilities. This would certainly be useful for testing and
> would likely be useful for applications using the library.
>
With some minor fixes to the original patch, here's where its at:
$ pmconfig -L
pmapi_version=2
multi_threaded=true
fault_injection=false
secure_sockets=true
Seems promising (nice & simple) so far, so I'll continue down this
path with NSS-conditional QA test updates today, man page updates,
etc.
With that, I think the next stage of NSS merging is looking really
good now; so planning to merge that into dev late today if nothing
unexpected happens.
cheers.
--
Nathan
|