Hi �?ric, On Sat, Sep 17, 2005 at 05:17:31 +0200, �?ric Bischoff wrote:
> > if used only during build time, put them in a Build section. > > Well, the list is currently for _runtime_ environment variables only. I doubt that, I don't think variables like SRC_ROOT, INCLUDE, SOLARSRC and the like would affect the OOo runtime. I may be wrong on this, of course. If all variables are obtained by some 'grep getenv' or similar, these probably indicate that a tool used during build time uses them. A column listing the place of occurence would help to determine this. > Even if both kinds of variable appear in the same source code, their usage is > completly different. One will never be able to tune the bahaviour of the > official RPM or MSI packages he/she downloads with build time variables ;-). Well, did you verify? Also build time variables might get used in the product to tweak some behavior for debug purposes.. > > But don't just remove > > them from the documentation. It might also be a good idea to introduce > > an "available since milestone" and a "removed in milestone" column. > > I personally tend to think it is less work _not_ to have these two new > columns, and that it keeps the list more legible. Without the information you don't know whether the variable is available in the release you have. But you're right, this can be always stated in the description field, we don't need separate columns for that. > (This is only a personal impression. Feel free to do any change in the > structure of the table if you think it is better.) I think we should somehow agree on the overall structure before everyone starts changing it.. Eike -- OOo/SO Calc core developer. Number formatter bedevilled I18N transpositionizer. GnuPG key 0x293C05FD: 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
