Feature request: "bzr check-install"
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Bazaar |
Wishlist
|
Unassigned | ||
Bug Description
affects /products/bzr
----- Forwarded message from Matthieu Moy <email address hidden> -----
From: Matthieu Moy <email address hidden>
Subject: Feature request: "bzr check-install"
Date: Wed, 31 May 2006 07:33:26 +0200
Hi,
I've just installed bzr on an "old" Fedora Core 2, which had none of
bzr's dependancies or recommandation as .rpm package.
It was quite a pain indeed: after "bzr" started to work, I still had
to install paramiko, which itself didn't work until I installed
pycrypto (giving no relevant error message, so a beginner would have
been completely lost here, but this is a known bug).
Then, I installed cElementTree because I knew it was nice to have it.
Something that would have considerably eased my life then would be a
command to check that the installation is complete. A kind of short
and user-friendly "bzr selftest":
$ bzr check-install
bzr works: yes
sftp works: no (missing pycrypto)
cElementTree installed: no (bzr will still run, but slower)
$
or
$ bzr check-install
bzr works: yes
sftp works: yes
cElementTree installed: yes
All dependancies and recommandations are satisfied
$
It should be relatively easy to implement, and would considerably
improve the first contact of beginners requiring to install bzr
themselves.
--
Matthieu
| Christopher Bayliss (baylisscg) wrote : | #1 |
| John A Meinel (jameinel) wrote : | #2 |
It could be nice to have a post-install dependency check.
We already do better about sftp errors for bzr-0.9 and beyond. But certainly we could have something that checks for cElementTree, paramiko, pycurl, etc. All of our soft dependencies.
| Changed in bzr: | |
| importance: | Undecided → Wishlist |
| status: | Unconfirmed → Confirmed |
| Alexander Belchenko (bialix) wrote : | #3 |
Someone could extend my pluign 'depend'. I use this pluign to verify standalone bzr.exe for presence of all required libraries.
| tags: | added: check-for-breezy |
Perhaps embedding warnings when a command is issued that isn't fully supported.
e.g. using
$ bzr checkout sftp://
without paramiko installed would give some sort of warning about not being able to do sftp
bzr: ERROR: Cannot perform sftp transfers without paramiko library installed.
bzr: WARN: Trying local filesystem path instead.
or
bzr: ERROR: Cannot perform sftp transfers in current state. See "bzr check-install" for details.
bzr: WARN: Trying local filesystem path instead.
Otherwise the user will be left wondering why something doesn't work as expected.