On Thursday 03 September 2009, Tino Schwarze wrote:
> > It would be bad from a discoverability standpoint to have some variables
> > be additive, and others ablative. They should all behave the same way;
> > and the only sensible way IMHO is current behavior.
>
> But maybe the global config could be made available as $GlobalConf{xyz}
> within the per-host config?
That also looks like a good alternative to me.
> I remember having tried the same thing - that is, I want a set of default
> excludes, then extend then for one host. Currently, I have to repeat the
> whole default config just to append one more directory to the excludes.
Same here.
--
D.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
