On Friday, October 31, 2003 at 3:15:06 PM,

    Clifford Wolf <> wrote:

> On Wed, 29 Oct 2003, Tobias C. Rittweiler wrote:

> > the bootdisk target sets LIMITCXX to 1, but other targets (like generic)
> > doesn't explicitely set it to 0 again. That causes possibly several build
> > errors (just for example it makes bdb3.3 fail).
> >
> > Should I use the bug tracking system for such trivial things, too?
>
> That _only_ happens if expert options are enabled. If expert options are
> disabled, all expert options are set to default values automatically, if
> not another value is forced using a ROCKCFGSET_... value.
>
> This is a known design issue and not trivial at all. 2.1 will have a
> rewritten config tool which will solve that issue. But at the moment I
> have no idea how, so suggestions are - as always - very welcome.

Well, I think it would be socially absolutely ok if choosing a target
meant that everything is set back to its default value (ie. doing almost
the same as what is done when there's no config yet. AFAICS, parsing
src/rockconfig.in is mainly responsible for that)

Your taste/perception (what's socially right) may differ, of course.
What do you think?


-- tcr () ``Ho chresim'eidos uch ho poll'eidos sophos''

-- 
To unsubscribe from this list: send a mail with the subject "unsubscribe
rock-linux" to <>. For more information about ROCK
Linux have a look at <https://www.rocklinux.org/>.