Jordi Vilalta wrote:
Hello again,
As I said in my previous mail, I'm using a common monotone repository
to group all the projects I follow. As the options for the repo are
mostly common for all the synced projects, there's a lot of duplicated
options: ...
Tailor already offers a simple solution: the [DEFAULT] section. What you
propose is configurable in the following way
[DEFAULT]
target-repository = myrepo.mtn
target-keyid = [EMAIL PROTECTED]
target-passphrase = lala
[monotone:projectA]
module = net.example.projectA
[monotone:projectB]
module = net.example.projectB
Anyway, I see that not all backends (monotone in particular in its
_load() method) uses that strategy. All options should be loaded with
something like
self.repository = cget(self.name, 'repository') or \
cget(self.name, '%s-repository' % self.which)
Here the code say "lookup either 'repository' or 'source-repository' (or
'target-repository'", first in the section describing the repository
(sorry for the bad wording), then in the [DEFAULT] one.
Since it was easy enough, I fixed the monotone backend :) A quick
inspection did not reveal other potential candidates, but feel free to
report other options that should follow this pattern.
And let me know if this works and smooths the path :)
hth,
ciao, lele.
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
