Re: Bug#786448: [RFR] templates://neurodebian/{neurodebian.templates}
Dear i18n team et al!
First of all thank you again for all your work/contributions! I thought
to jump on addressing them all right away but other RL duties
overwhelmed me. I hope to actually take care about this in 2 weeks when
I get back and schedule normalizes. Meanwhile my few comments are
inlined below with hope to boil down the optimal patch. BTW -- if
easier, neurodebian package is available also from github
(https://github.com/neurodebian/neurodebian/) so if you are working
within git -- feel more than welcome to send a PR with the changes to
be merged.
On Thu, 04 Jun 2015, Justin B Rye wrote:
> Christian PERRIER wrote:
> > It's indeed hard to detail each and every proposed changes : there are
> > many because the original files had to be both reviewed for English
> > usage....and also using the standardized writing style we usually
> > recommend.
> > The same stands for debian/control.
> > --- neurodebian.old/debian/neurodebian.templates 2015-05-21 21:14:37.627014717 +0200
> > +++ neurodebian/debian/neurodebian.templates 2015-06-04 10:07:49.400262065 +0200
> > @@ -5,26 +5,30 @@
> > Template: neurodebian/enable
> > Type: boolean
> > Default: false
> > -_Description: Should NeuroDebian repository be enabled?
> > +_Description: Enable the NeuroDebian packages repository?
> Make that "package repository".
wouldn't it collide with "NeuroDebian package" as if it is only about
that package (or packages for that sake)?
> > - NeuroDebian project provides a separate APT repository with backport
> > - builds of most recent releases of maintained software, datasets and
> > - some software not in Debian proper yet. Enabling this additional
> > - repository will make those packages available on your base system.
> > + The NeuroDebian project provides a separate APT repository with
> > + the most recent releases of maintained software and datasets as
> > + well as software that is not yet provided in Debian.
> Are we avoiding the phrase "backport builds" on the basis that it's
> developer jargon? The trouble is, backports aren't necessarily the
> same thing as "the most recent releases". And does "maintained
> software" mean "some software (which we're maintaining)" or "only the
> software that's maintained"? And doesn't the category "software that
> is not yet provided in Debian" also cover both the backports and
> datasets?
first to clarify: some software packages we are not directly
maintaining ourselves (thus "we're maintaining" would be misleading) --
some are maintained by upstream authors, some we simply re-build
to provide backports from current testing.
To address your comment about "the most recent", I would be ok
rephrasing "the most recent releases" into "recent releases".
I am ok to avoid "backports" (since we also have "standalone" and
"sloppy" builds ;) )
> Maybe we should just say:
> The NeuroDebian project provides a separate APT repository with
> software that is not available in Debian, including datasets and
> backported new releases.
This phrasing imho misleads a bit since majority of the software we
provide from NeuroDebian IS available in Debian (we aim to upload to sid
and NeuroDebian at the same time), just possibly of previous
releases.
> I should hope by the time they're reading this users would already
> know what NeuroDebian is anyway.
> > + .
> > + If you choose this option, those packages will be available
> > + for upgrades and installation.
> Minor tweaks:
> .
> If you choose this option, these packages will be available for
> installation and upgrades.
> > - .
> > - Note: although NeuroDebian team aims to assure robust and correct
> > - operation of provided packages, enabling this additional archive
> > - might compromise the integrity of your base system.
> > + .
> > + Even though these packages are closely maintained
> > + by the NeuroDebian team, enabling this additional archive
> > + may compromise the integrity of the system.
> OK.
> > Template: neurodebian/release
> > Type: select
> > -Choices: auto, ${releases}
> > +__Choices: automatic, ${releases}
> > +Choices-C: auto, ${releases}
> Oh, one of these.
any preference? ;)
> > Default: auto
> > _Description: Release name of the base system:
> > - Specify for which Debian or Ubuntu release (e.g. wheezy or trusty).
> > + Please specify the relevant Debian or Ubuntu release name
> > + (for instance "wheezy" or "trusty").
> It's not immediately obvious what the name would be "relevant"
> to; how about
> Please specify the appropriate Debian or Ubuntu release codename
> (for instance "stretch" or "trusty").
> (Updating the Debian codename just for futureproofing.)
yeah -- sounds good
> > .
> > - If 'auto', Debian or Ubuntu release name will be '${release}' as
> > - deduced from the output of apt-cache policy. If the release of your
> > - system is not '${release}' -- please choose specific one which
> > + If this is set to "automatic"', the release name is chosen
> > + after the output of "apt-cache policy". If the release name
> > + for this system is not "${release}", you should choose specific one which
> > matches best.
> s/after/according to/
> s/choose specific one/choose the specific one/
good with me
> > Template: neurodebian/mirror
> > Type: select
> > Choices: origin, best, custom, ${mirrors}
> > Default: best
> > _Description: NeuroDebian mirror to use:
> > - NeuroDebian project has a number of community-maintainer mirrors
> > + NeuroDebian project has a number of community-maintained mirrors
> > around the globe.
> ^The^ NeuroDebian project.
yeap!
> [...]
and uff -- sorry, need to run... will review more later. Thanks
again!!!
--
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Research Scientist, Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
Reply to: