Re: compile-time configuration, etc.

"D. J. Bernstein" <[email protected]> wrote:
> Installing the package shouldn't touch the user's preexisting
> configuration.
>
> The name ``conf-cc'' in some of my current packages is a misleading
> historical relic. The packages do not, in fact, support configuration of
> the compiler.

Not by your definition of "support", apparently.  But let's not argue
about definitions.  Whatever you call conf-cc, it has the properties I
described, and I think those properties are useful.  There could be
other ways of doing things that would be more useful, but I don't
think Stefan's way is it, and I'm not entirely sure what your way
would be.  The problem goes beyond compiler flags - e.g., non-root
users installing packages in their home directories may have to change
dependency package paths; how would you handle that?  What about
things like nistp224's conf-opt?


paul