[tahoe-dev] Trouble compiling on OSX

Zooko O'Whielacronx zooko at zooko.com
Thu Aug 4 13:47:16 UTC 2011


On Wed, Aug 3, 2011 at 10:51 PM, Olaf TNSB
<still.another.person at gmail.com> wrote:
>
> When I don't have 'darcs' in my path I get the following output:
> running darcsver
> setup.py darcsver: didn't find version tags with darcs, and
> ['src/allmydata/_version.py'] don't exist.
>
> However, when I copy darcs into my path...
> running darcsver
> setup.py darcsver: wrote '1.8.2-103' into src/allmydata/_version.py
>
> I'd suggest a kinda:  if exists(darcs) ... else ...   code block.

There is one. This is the way it is supposed to work. If you have
darcs in your patch then it generates the version number from darcs
history, and if it doesn't then it uses whatever version number is
left in src/allmydata/_version.py. (Brian Warner came up with this
design in about 2006.)

Therefore, people who redistribute tahoe-lafs in some container which
isn't a darcs repository should include a src/allmydata/_version.py
with it. If they don't, you'll get "version == 'unknown'". Those tests
that you saw fail are there to make sure that someone isn't running a
Tahoe-LAFS build with "version == 'unknown'". :-)

So, maybe Brian's git mirror should have a src/allmydata/_version.py
in it. We'll think about this more after the 1.9 release. By the way,
there is a darcs Google Summer of Code to add a bidirectional
darcs-to-git gateway:

http://blog.owenstephens.co.uk/201107/gsoc-darcs-bridge-%E2%80%93-detecting-merges

That might be useful for us (assuming it works as advertised).

Regards,

Zooko



More information about the tahoe-dev mailing list