[OpenAFS-devel] RxOSD configure option
Russ Allbery
rra@stanford.edu
Mon, 20 Jul 2009 07:48:04 -0700
Simon Wilkinson <sxw@inf.ed.ac.uk> writes:
> Personally, I'm clean to avoid #ifdefs wherever possible. They
> dramatically complicate the testing process, and mean that packagers
> have to make decisions on behalf of end users. They're appropriate for
> items in the development stream, where people may want to test one piece
> of code, but not another, but I'm strongly opposed to large numbers of
> --enable switches appearing in the production code.
Amen. I want to get rid of most of the ones we already have.
> Also, it's vital that it's impossible to shoot yourself in the foot by
> accidentally installing a non-rxosd server on a rxosd machine, or vice
> versa. This means that even if you do end up using configure switches,
> both versions have to equally aware of each other's data to correctly
> preserve it.
Ideally, all things like this should be run-time options, not compile-time
options.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>