Source: gcl27
Version: 2.7.1-3
Severity: normal
Since the last update you have the follwoing sentence in Debconf:
You can locally override this choice by setting the GCL_ANSI
environment variable to any string but \"no\" for the ANSI build,
and to \"no\" for the CLtL1 build, e.g. GCL_ANSI=t gcl27.
1) This sentence is not clear.
If I want to override this choice I can set *any* string except "no"?
So foobar, yes, nein … will override it?
2) The option "no" is *both* for the ANSI build *and* the CLtL1 build?
I *strongly* suggest running your template over debian-l10n-english
for a quick round of additional review and than issue a call for
translation updates, I can help you on the latter if you are short on
time, especially since the freeze is in progress.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Greetings, and thanks so much for your feedback! I think the sentence
is intelligible, but could be reworded to increase clarity. The meaning
is that the user can override the default selection of lisp image in
debconf using the GCL_ANSI environment variable at runtime. Setting to
"no" will select the CLtL1 image regardless of debconf setting, and
setting it to any other string will select the ANSI image regardless of debconf setting.
gcl27 (and dependency axiom) will migrate right before the hard freeze
on 5/15. Most likely this will have to wait until after the freeze, but
if you can convince the release managers to accept another upload
containing a rewording before then with no migration timetable penalty,
I can certainly help out.
Helge Kreutzmann <debian@helgefjell.de> writes:
Source: gcl27
Version: 2.7.1-3
Severity: normal
Since the last update you have the follwoing sentence in Debconf:
You can locally override this choice by setting the GCL_ANSI
environment variable to any string but \"no\" for the ANSI build,
and to \"no\" for the CLtL1 build, e.g. GCL_ANSI=t gcl27.
1) This sentence is not clear.
If I want to override this choice I can set *any* string except "no"?
So foobar, yes, nein … will override it?
2) The option "no" is *both* for the ANSI build *and* the CLtL1 build?
I *strongly* suggest running your template over debian-l10n-english
for a quick round of additional review and than issue a call for translation updates, I can help you on the latter if you are short on
time, especially since the freeze is in progress.
Hello Camm,
Yes, I would suggest improving the clarity, especially since "no" is mentioned for both cases (see below).
You can locally override this choice by setting the GCL_ANSI
environment variable to any string but \"no\" for the ANSI build,
and to \"no\" for the CLtL1 build, e.g. GCL_ANSI=t gcl27.
2) The option "no" is *both* for the ANSI build *and* the CLtL1 build?
Greetings! More on the rest of your note later, but:
Helge Kreutzmann <debian@helgefjell.de> writes:
Hello Camm,
Yes, I would suggest improving the clarity, especially since "no" is mentioned for both cases (see below).
You can locally override this choice by setting the GCL_ANSI
environment variable to any string but \"no\" for the ANSI build,
and to \"no\" for the CLtL1 build, e.g. GCL_ANSI=t gcl27.
2) The option "no" is *both* for the ANSI build *and* the CLtL1 build?
The string "no" is not for both cases -- for ANSI, GCL_ANSI can be set
to any string *but* "no" (i.e. *except* "no"); for CLtL1, GCL_ANSI is
set *to* "no". Am I missing something?
Greetings! More on the rest of your note later, but:
Helge Kreutzmann <debian@helgefjell.de> writes:
Hello Camm,
Yes, I would suggest improving the clarity, especially since "no" is mentioned for both cases (see below).
You can locally override this choice by setting the GCL_ANSI
environment variable to any string but \"no\" for the ANSI build,
and to \"no\" for the CLtL1 build, e.g. GCL_ANSI=t gcl27.
2) The option "no" is *both* for the ANSI build *and* the CLtL1 build?
The string "no" is not for both cases -- for ANSI, GCL_ANSI can be set
to any string *but* "no" (i.e. *except* "no"); for CLtL1, GCL_ANSI is
set *to* "no". Am I missing something?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 491 |
Nodes: | 16 (2 / 14) |
Uptime: | 108:19:45 |
Calls: | 9,684 |
Files: | 13,725 |
Messages: | 6,175,598 |