As these locations would be the canonical locations for Ubuntu packages I agree "ubuntu:" is appropriate for the Ubuntu packages. I think using "debian:" for the Debian packages is confusing. E.g. "debian:samba4" on Debian systems would fetch from Launchpad while the primary branch is hosted on alioth and has a completely different revision history. Contributors can only submit bundles against the branch on alioth. What about something like "lp-debian:"?
"vcs:" might be confusing on e.g. Fedora systems with bzr installed. Perhaps "apt:" or "apt-vcs:" ?
Using single letters for Debian releases is a bad idea imho, there is some overlap there (e.g. sid and squeeze, etch and experimental) that is only confusing.
Just a thought; Given these add directory services are specific to Launchpad and don't rely on anything else in builddeb it seems to me that the Launchpad plugin would be a more appropriate place for them. That way people not using bzr-builddeb would also be able to use them, and they are less prone to break because of changes in bzrlib.plugins.launchpad.
Hi Barry!
Nice to see these two extra aliases.
As these locations would be the canonical locations for Ubuntu packages I agree "ubuntu:" is appropriate for the Ubuntu packages. I think using "debian:" for the Debian packages is confusing. E.g. "debian:samba4" on Debian systems would fetch from Launchpad while the primary branch is hosted on alioth and has a completely different revision history. Contributors can only submit bundles against the branch on alioth. What about something like "lp-debian:"?
"vcs:" might be confusing on e.g. Fedora systems with bzr installed. Perhaps "apt:" or "apt-vcs:" ?
Using single letters for Debian releases is a bad idea imho, there is some overlap there (e.g. sid and squeeze, etch and experimental) that is only confusing.
Just a thought; Given these add directory services are specific to Launchpad and don't rely on anything else in builddeb it seems to me that the Launchpad plugin would be a more appropriate place for them. That way people not using bzr-builddeb would also be able to use them, and they are less prone to break because of changes in bzrlib. plugins. launchpad.