Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#3791 closed enhancement (invalid)

Subversion client for BeOS on website is out-of-date

Reported by: haiqu Owned by: haiku-web
Priority: normal Milestone: R1
Component: Website Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

Tried to do an `svn cleanup' on sources downloaded via Haiku and found this problem:

Welcome to the BeOS shell.

$ cd /Stick/src/haiku
$ svn cleanup
svn: This client is too old to work with working copy ''; please get a newer Subversion client

This means that the subversion client for BeOS on the website's "Getting Started" page is outdated and needs revision.

Change History (9)

comment:1 by haiqu, 10 years ago

Attempted to build this but it's a bit frobbity. Subversion requires:

apr - built apr-util - built neon (optional, not built) sqlite3.c - failed build, requires pthreads

Argh!! GNU dependency hell ...

in reply to:  1 comment:2 by bonefish, 10 years ago

Resolution: invalid
Status: newclosed

Replying to haiqu:

Attempted to build this but it's a bit frobbity. Subversion requires:

apr - built apr-util - built neon (optional, not built) sqlite3.c - failed build, requires pthreads

Argh!! GNU dependency hell ...

Only neon is GNU actually. And using existing components to avoid reimplementing wheels is just how software development works.

Anyway, closing as invalid, as the svn BeOS port works fine, you just can't use working copies checked out by newer clients. I generally don't consider it our responsibility to keep BeOS ports up to date.

comment:3 by haiqu, 10 years ago

They're usually included unless there is a licensing conflict. In fact it also needed zlib ... *sigh*.

Point taken about it not being the responsibility of Haiku team to keep BeOS tools up-to-date. However since no-one else seems to be taking responsibility for this, the load falls back on us unless/until we get to being a self-sustained, stable and independent platform with CD images available, i.e. R1 release.

I won't re-open, but will post the file here should I eventually get it to build.

comment:4 by haiqu, 10 years ago

Oh, and FYI I did manage to get a complete build of svn-1.6.0 on Haiku if anyone wants to update the current svn-1.4.6 build.

comment:5 by anevilyak, 10 years ago

Replying to haiqu:

Point taken about it not being the responsibility of Haiku team to keep BeOS tools up-to-date. However since no-one else seems to be taking responsibility for this, the load falls back on us unless/until we get to being a self-sustained, stable and independent platform with CD images available, i.e. R1 release.

Why? There's utterly no need to. The subversion client for R5 is entirely capable of checking out and working with the tree. The problem you're seeing is a general subversion problem because the svn team doesn't even remotely bother trying to keep back compat on the internal format of the .svn metadata directories. As such, *any* two major revisions of the svn client are mutually incapable of working with each other's checkouts, regardless of platform.

comment:6 by umccullough, 10 years ago

Furthermore, Haiku is pretty much already an independent platform, I know of very few who depend on BeOS for their Haiku development/usage. In fact, Linux/FreeBSD makes a MUCH better platform to build/install Haiku from at this point.

IMO, prolonging BeOS usability "because Haiku isn't ready yet" doesn't actually help Haiku get any better at all - it just allows the die-hards to continue using BeOS while they could be testing/fixing Haiku instead.

comment:7 by haiqu, 10 years ago

Interesting comments from both Rene and Urias there.

The glories of developing from within Linux have already been espoused elsewhere. However, one then lacks a reference platform for compatibility testing, which is present when developing from BeOS. I also have no intention of ever using Linux or BSD again for a working environment, so installing it wasn't ever an option.

The compatibility issues between versions of Subversion are precisely the reason we need a working (minimum) svn-1.4.6-beos build. Currently the BeOS version used is svn-1.1.3 which is a dinosaur. Keeping a single copy of the repository sources on an external drive - in my case, a USB memory stick - and accessing it from both systems ensures that I don't get glitches caused from building an incomplete source tree, and also saves having to svn up from two different operating systems.

So, that's my reasoning anyhow.

comment:8 by mmlr, 10 years ago

Really, if you don't want to install Linux or BSD (and I understand why one wouldn't want to, I haven't installed either), I strongly suggest using Haiku as your development platform instead of BeOS. Even if there was a more current subversion client for BeOS (here's a 1.4.6 for BONE anyway: http://haiku.mlotz.ch/subversion-1.4.6-bone.zip) it's just painfully slow on BeOS. You get update times in the minutes, if not tens of minutes, for no real benefit. Even if Haiku is still slower than other systems, it's numerous times faster than BeOS for most tasks and especially for file operations and for compiling (due mostly to the better cache). I use Haiku full time here as my main operating system and that includes Haiku development and I know that other devs have migrated to Haiku for Haiku development as well.

comment:9 by haiqu, 10 years ago

Hi Michael,

I'm seriously trying to use Haiku as a primary development environment but had some HDD troubles, although in the last few days things seem to have improved. Copying the source files from one disk to another was taking 6-8 hours last week.

Thanks for the link to svn-1.4.6-bone but I'm booting BeOS 5.0.3 Pro (sans BONE) right now, and that's where all the files are located. I've downloaded it anyhow in case I ever decide to run from Dan0 or install Bone7 again.

Things will improve shortly as I build all the bits required, and I expect to be running full-time from Haiku any time now.

Note: See TracTickets for help on using tickets.