baz-import test requires 'testresources'

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Arbash Meinel wrote:
> Martin Pool wrote:
> 
>>On 12 Dec 2005, John Arbash Meinel <john at arbash-meinel.com> wrote:
>>
>>
>>>The baz-import test suite tries to import something called "testresources".
>>>This is a module/package that I don't have installed on my system. Is it
>>>a 3rd party toolset that is available?
>>>I tried looking in Ubuntu Synaptic, and I didn't find anything called
>>>"testresources".
>>>
>>>I want to work on writing a test case for my "--continue-on-errors"
>>>flag, but as it stands I can't run the test suite.
>>
>>
>>I think this is Robert's module. 
> 
> 
> Is it something publicly accessible?

Yes.  The bzr branch is here:
http://www.robertcollins.net/unittest/testresources

 For something as 'core' as
> bzrtools, should it be depending on a not-generally-available module?

Umm, I don't know how to cope with this statement.  Now that there's
native push, bzrtools isn't actually required for basic operations, and
that was always the intent.  It's not core, and the barrier-to-entry is
lower.

And you're talking about the requirements of Robert's branch-- the
mainline does not (yet) have this requirement, because Robert has
declared that his branch isn't ready to be merged.

I think he did say that testresources should be optional, at one point.

> I think we could restrict IDs

We certainly can, but that simply moves the encoding/decoding into
baz-import, and means that any other tool that wants meaningful ids,
(e.g. Tailor, foreign branches) need to perform their own conversions.

> because they aren't meant to convey
> information directly

I am trying to convey information directly, using them.  Specifically, I
am trying to convey "This revision was converted from Arch revision FOO
using algorithm bar".  This is useful to both users and tools.  If the
encoding is done by baz-import, then the tools users typically use that
show revision IDs (log, cat-revision) will be unable to produce the
unencoded form.

> (they happen to have usernames, but more for
> uniqueness than because we are trying to tell someone something).

They have both usernames and filenames, and I've found both useful in
debugging.  Heck, we can still tell who's to blame for the two ghost
revisions in the bzr tree. :-)

> Can email addresses have non-ASCII characters? I'm thinking someone like
> Erik Bagfors (sorry about not marking the a, I don't know how to do it).

You can have unicode domain names, can't you?   Ahh, the joys of Punycode.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDnulq0F+nu1YWqI0RAnoaAJ9KW4RC7gb/auJpHWOWcuPAaWNoxgCfSzWO
YZDZvP1JKDJR1U+MRvh/oJs=
=U3HB
-----END PGP SIGNATURE-----