[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [ITR] templates://apt-cacher-ng/{apt-cacher-ng.templates}

Eduard Bloch wrote:
> Ok, I suggest the following versions of the files. There were some
> conflicting opinions in the previous discussion but I hope to have found
> the best compromise between clarity and verbosity. If you agree, I would
> like to release the new package version RSN.
> Template: apt-cacher-ng/gentargetmode
> Type: select
> _Choices: Setup once, Setup now and update later, No automated setup
> _Default: Setup once

s/Setup/Set up/ (where it's a verb; in "automated setup" it's a
noun, so okay)

> _Description: Preconfigure apt-cacher-ng for transparent requests source rerouting?

"Transparent requests source rerouting" is hard to make any sense
out of, and reading the documentation doesn't help, since it doesn't
use this term "rerouting" at all.  Instead, anything more complex
than plain proxying (which you've told us isn't what you mean here)
is referred to in the docs as "URL remapping".  Could you use the
same terminology here?

  _Description: Configure apt-cacher-ng to use URL remapping?

>  Apt-cacher-ng can request packages from a mirror of your choosing, instead of
>  the one requested by the client. One possible use of this feature is quick
>  changing of the real download mirror for all users without modifying every
>  single client system. To configure it, sets of source mirrors need to be
>  configured for various distributions.

That's promising, but then ends up unclear.  I need to configure
source mirrors for... "various distributions"?  Maybe you mean:

   single client system. To configure it, a set of URL remappings
   needs to be set up for each APT source.

(An example might help.)

>  .
>  During the package installation, this sets can be prepared based on the
>  current state of /etc/apt/sources.list. Optionally, this process can be
>  repeated on every package update (modifying configuration files later).

I think I understand most of this, except for the last parenthesised
section which I'll have to guess at.  Is it: 

   These sets can be prepared now, based on the current state of
   /etc/apt/sources.list. Optionally, this process can be repeated on
   every package update (modifying the configuration files each time).

>  .
>  NOTE: selecting "No automated setup" can leave previously created mirror
>  configuration behind, which needs to be updated by cache administrator manually.

  If you select "No automated setup", any updates to an existing
  configuration will need to be performed manually.

In the control file, you've just reverted to the original.  Instead
make it:

  Description: caching proxy for APT sources         
   Apt-Cacher NG is yet another implementation of an HTTP proxy for
   Debian-style software repositories.
   It follows principles similar to many other solutions and serves the
   same purpose: a central machine hosts the proxy for a local network,
   and clients configure their APT setup to download through it.
   Apt-Cacher NG keeps a copy of all useful data that passes through
   it, and when a similar request is made, the cached copy of the data
   is delivered without being re-downloaded.
   Apt-Cacher NG has been designed from scratch as a replacement for
   apt-cacher, but with a focus on maximizing throughput with low system
   resource requirements.

JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package

Reply to: