subversion: all or none?

Friday, Dec 23. 2005  –  Category: OpenSolaris, OpenSource

i think i’ve got the incremental “squelch”-ing working now, so i can maintain a per-putback squelched workspace that mirrours ON. this puts us one step closer to being able to do nightly source syncs.

my next step is to somehow mirrour this over to Subversion. i’m running into a problem though… Subversion requires you to checkout whole directories. you can’t just checkout/edit one file. this isn’t a problem when you’re editing usr/src/cmd/ps/Makefile – but becomes annoying when you want to edit usr/src/Makefile.master.

why do i have to checkout everything in usr/src? that’s thousands of files i have to unnecessarily checkout when all i want to do is edit one file.

i know SCCS is old – but the more i use other SCMs, the more i like SCCS :-P

No Trackbacks to “subversion: all or none?”

3 Comments to “subversion: all or none?”

  1. Cyril Plisko Says:
    December 23rd, 2005 at 13:56

    It takes some time to get into Subversion :) At least it took for me – I spent a lot of time with TeamWare before first Subversion experience. The Subversion working copy is like TeamWare workspace – it supposed to be a long live entity. Once you created it by “svn co” it is for your own use. However, no files are actually “check-out” in an SCCS sense. After you’ve done with your editing you can check-in back whatever you want – it can be the whole working copy, or one single file, or anything in between. So for what you trying to achieve I think you should just create a working copy and then edit and check-in files as needed. You just never remove your working copy. Of course it is a matter of how fast the whole working copy can be recreated. For example at svn.genunix.org it takes me around a minute to “svn co” the whole opensolaris tree. So the operation is cheap and I never keep the working copy for longer then an hour when I am merging the next OpenSolaris codedrop. On my laptop however checking out the full trunk from the svn.genunix.org takes much longer and, hence, the working copy tends to live for days if not weeks usually. Anyway, if you feel like talking about SVN experience WRT OpenSolaris feel free to mail/irc me.

  2. Stephen Lau Says:
    December 23rd, 2005 at 17:36

    hey cyril, thanks – yeah, i’m too used to the SCCS/TeamWare model which lets you just bringover what you want, edit it – put it back and nuke your workspace. i’ve got a test setup now that keeps a long-lived Subversion workspace around now and just works within that. It just bugs me though because now I need to keep 3 full copies of ON around:

    1) a “squelched” TeamWare workspace 2) the SVN repository itself 3) a checked out copy of the SVN repository as my working copy

    anyway, disk space is cheap – so I suppose it’s not too big a deal, but still.. :-)

  3. Cyril Plisko Says:
    December 24th, 2005 at 13:23

    May I suggest working against svn.genunix.org repository ? Although the repository itself consumes only a few hundreds MB – peanuts comparing to the WC.

Leave a Reply

Recent posts

Categories

Grommit

Mozilla

OpenSolaris

Songbird

Archives

Meta