On 02/16/04  Thomas de Grenier de Latour wrote:

> I agree more options are needed, but i think a minimal set of defaults
> that user can't change is a good thing (there is no point to change
> most of options that are currently default in fact). Also, options
> like verbosity and progress meter make more sense when controlled on
> command line using -v/-q and --nospinner from emerge than in a
> configuration file. So imho, RSYNC_OPTIONS should more be called
> RSYNC_EXTRA_OPTIONS, with default well documented so that we know what
> are options really left to customization.
> 
> Another approach would be to have an /etc/portage/rsync.conf with
> detailed option like the ones currently in make.conf, but more
> numerous. This would ensure that only non-default options are modified
> by user, and would solve the transition problem (because new config
> files are always merged whereas make.conf updates are often ignored).
> Or does this sound too "make.conf.d-ish"?

One reason why I asked this is because I'm working on `emerge --sync`
support for overlays and using RSYNC_OPTIONS (or RSYNC_EXTRA_OPTIONS)
would make that a lot easier to implement different options for
different trees.

Marius

-- 
Public Key at http://www.genone.de/info/gpg-key.pub

In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to