Author Topic: Note on revisions when compiling Code::Blocks  (Read 3246 times)

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Note on revisions when compiling Code::Blocks
« on: November 10, 2006, 01:12:15 pm »
As of today (this will be committed after Yiannis has finished moving around a few directories),
autorevision will no longer support anything but Subversion version 1.3 and upwards.

Support for manually parsing the entries file has been abandoned alltogether, and autorevision now demands XML output from svn. XML output is not supported prior to Subversion 1.3.0.

If you do not have a recent enough svn client installed on your machine, you will of course still be able to compile Code::Blocks. However, the revision will show as "0" and the revision date will be empty.

Though this may be an inconvenience for some, it is something you have to live with. The never-ending issues with parsing human-readable, localised data in unknown encodings have become unbearable. XML should ensure that no such issues come up again in the future.
This comes at the price of requiring everybody to use a Subversion client that's not older than 11 months, which I think is an acceptable fee for avoiding all that grief.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: Note on revisions when compiling Code::Blocks
« Reply #1 on: November 10, 2006, 01:28:45 pm »
Quote
As of today (this will be committed after Yiannis has finished moving around a few directories)

Just a note: this won't happen today but soon...
Be patient!
This bug will be fixed soon...

Offline afb

  • Developer
  • Lives here!
  • *****
  • Posts: 884
Re: Note on revisions when compiling Code::Blocks
« Reply #2 on: November 10, 2006, 03:10:55 pm »
I have made a patch to generate both revision.m4 and src/sdk/autorevision.h,
so that we can make a "dist" tarball with everything pre-configured for a revision.

That is: you will still need SVN to generate the tarball, but then then the tarball
(like codeblocks-trunk-revXXXX.tar.gz) should be ready to use - without SVN.

Assuming that you use autotools, that is... (i.e. the ./configure && make thing)
It should also work for building RPMs, since we can bundled codeblocks.spec too.

Will clean up and post.

Offline afb

  • Developer
  • Lives here!
  • *****
  • Posts: 884