[tahoe-dev] Trouble compiling on OSX

Olaf TNSB still.another.person at gmail.com
Thu Aug 4 22:14:13 UTC 2011


On 04/08/2011 11:47 PM, "Zooko O'Whielacronx" <zooko at zooko.com> wrote:
>
> > 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'". :-)

I think the problem is that when someone (i.e. me!) gets the code from the
repo but doesn't have darcs. In that case would _version.py be populated?

I get the feeling I am just hitting a complete edge case that is _really_
rare.  What are the odds of someone getting the code from the repo _without_
having darcs. Most people without darcs would prob be getting pre-packaged
code.

I just like being difficult...  :)

Olaf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20110805/c4c7bf84/attachment.html>


More information about the tahoe-dev mailing list