Quoting Noel David Torres Taño (envite@rolamasao.org):
> > Template: kstars-data-extra/kstarsrc-title
> > Type: title
> > -_Description: kstars global config file
> > +_Description: Handling of kstars configuration file
> >
> > I have to mention that I'm not entirely fond of the overuse of
> > db_title. I think that the default title ("Configuration of <foo>")
> > fits its needs.
> >
> > Anyway, I'w rewording to avoid the leading lowercase.
> >
> I think the word 'global' here is important for two reasons:
> a) the file will affect the behaviour of the kstars program, and it is the
> same file I will use in other kstars-data-extra-* packages
> b) the file is the system-wide configuration of kstars, there are other
> configurations per-user
For b) : Sure, I noticed that, but it is really expected that something
configuring stuff with debconf does this globally, so I kinda don't
feel the need for that "global" word
For a) this is what the title I propose says. It talks about "kstars
configuration file". I'm note sure we really need to make it overcomplicated.
> >
> [...]
> > Template: kstars-data-extra/disable-downloads-title
> > Type: title
> > @@ -27,21 +31,22 @@
> > Type: select
> > __Choices: keep enabled, disable, lock
> > Default: lock
> > -_Description: Disable downloads of new data for kstars users?
> > - Each user will be able to re-enable downloads for him unless you lock the
> > feature. +_Description: Choice for downloads of new data by kstars users:
> > + By default, unless the feature is locked, each user will be able
> > + to enable data downloads.
> >
> > Same "problem" with interrogative form.
> >
> > I admit that, here, I don't really understand the difference between
> > "disable" and "lock" and so would probably other users.
> >
> > Maybe the consequences of each option should be explained.
>
> I will explain here, so you can rephrase them and put in good english. If
> downloads are _disabled_, users CAN re-enable downloads by manually tweaking
> their own .kstarsrc files. If downloads are _locked_, users CAN NOT reenable
> them by any means (besides recompilation ;) )
>
> Why would users re-enable downloads? Because this setting affects all kstars
> downloads, not only those of Tycho2 catalog, disabling them all, while the
> package provides only the Tycho2 catalog datafile. There will be other
> packages in the future providing the remaining datafiles.
OK, that's clearer in my mind. Here is what I come up with:
Template: kstars-data-extra/disable-downloads
Type: select
__Choices: keep enabled, disable, lock
Default: lock
_Description: Choice for downloads of new data by kstars users:
By default, unless the feature is locked or disabled, each user will be able
to enable data downloads.
.
If you choose "keep enabled", users will be able to download data
files. If you choose "disable", each user can re-enable data download
(for instance to download data from other catalogs than Tycho2). If you choose
"lock", no user can enable data downloads.
Attachment:
signature.asc
Description: Digital signature