Christian Boos wrote: > The question is, should we fix that now, knowing this will have some > performance cost, as we need to know about the toplevel entries of the > default repository, or can we leave things as they are?
+1 for keeping the current behavior. There's no clear advantage to either, so the more efficient solution seems to be best. We should document it, of course. > Maybe the solution would be to check for such conflicts when doing a > "repository add" and a "repository list", and issue a warning when one > is found? I don't think this is worth the trouble for "repository add", as you could add a new repository and not have a conflict, then add a directory to the default repos with the same name, and you wouldn't be warned in that case. A warning with "repository list" and in the "Repositories" admin panel would be nice, though. -- Remy
signature.asc
Description: OpenPGP digital signature
