also sprach Rob Weir <[EMAIL PROTECTED]> [2005.07.23.1530 +0200]: > Why are you trying to specify a name for it? Bazaar doesn't really do > this anymore; instead, you have multiple locations for the one name, and > bazaar figures out which to use based on context.
I am not sure I follow, but it sounds cool. So let's take the classic case: I have an archive accessible via read-only WebDAV as well as sftp. Previously, I would register the first with an "-anon" suffix, and the second normally. This would allow me to commit to an archive from the same machine where I could also use cron to sync automatically (using password-less WebDAV). Since I cannot specify a suffix anymore and am thus bound to using the official name of the archive, I try to register both successively, but I find that they overwrite each other: cirrus:~> baz --version baz Bazaar version 1.4.1 ([EMAIL PROTECTED]/dists--bazaar--1.4[bazaar--devo.cfg] [...] cirrus:~> baz register-archive -d [EMAIL PROTECTED] [364] cirrus:~> baz register-archive http://arch.madduck.net/~madduck/pub/debianbook/ [365] Registering Archive: [EMAIL PROTECTED] cirrus:~> baz register-archive sftp://[EMAIL PROTECTED]/srv/arch/madduck/pub/debianbook Registering Archive: [EMAIL PROTECTED] cirrus:~> baz archives | grep -A2 [EMAIL PROTECTED] [367] [EMAIL PROTECTED] http://arch.madduck.net/~madduck/pub/debianbook/ [EMAIL PROTECTED] This is a real shame, because it effectively loses the extra layer of abstraction of the archive name. I really enjoyed being able to register an archive as "zope-upstream-archive-anon" and just use that name instead of the [EMAIL PROTECTED] crap. Why do you require the archive name I use on my work machine to be bound to the upstream name? -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver! the remote desktop feature of windows xp is really nice (and *novel*!). a micro$oft consultant can *remotely* disable the personal firewall and control the system. we'll ignore the fact that this tampering with the firewall is not logged, and more importantly, that the firewall isn't restored when the clowns from redmond are done with their job.
signature.asc
Description: Digital signature
