We were fed up about that and we made sure that we can work off line (and not checking all the repositories on earth) in 3.0 with esteban
On Oct 3, 2013, at 4:22 PM, Sven Van Caekenberghe <[email protected]> wrote: > Yes, that is what Monticello does on a save: check for potential name > conflicts in all linked repositories. It is just the way it is. It is not a > 100% foolproof way to guarantee uniqueness, but it will help in certain cases. > > We once thought about making this check optional (and a setting). > > One way out might be to remove all but the package-cache from the > repositories linked to your package, but I haven't tried. > > On 03 Oct 2013, at 15:58, "[email protected]" <[email protected]> wrote: > >> Hello, >> >> Monticello goes fetching a unique number in the previous version of a given >> package on Smallatkhub and that means requiring network access. >> >> Why is it so? >> >> I was working without network access and this bite me. >> >> I was able to get out of trouble with my Phone as an access point. >> >> But for some scenarios (w/ security and no external network access) this is >> really a pain. >> >> Also, the fact that I had to do a Cmd-. to get out of this is annyoying. >> >> Clues? >> >> Phil > >
