Comments on: Powerbuilder work with SVN, CVS on SourceForge

By: Frank Mao

Frank Mao — Mon, 07 Sep 2009 18:05:58 +0000

That’s why you need PBG files for, which keeps the mapping info between sr* and pbl.

PBG is auto-gened by PB IDE when you first time connect to any source control system, vss or svn. It can be messed up by developers or env. So you need a CI to check it constantly.

By: Galaxis

Galaxis — Mon, 07 Sep 2009 17:52:51 +0000

I meant if you don’t extract them from the PBL 1st and store them separately. You mean SVN knows how to parse Sybase PBLs, extract the indivual sr* files, and store/version them individually? Or are you using some 3rd-party interface (like PushOK) and it’s digging into the PBL? That would be a great advantage to know.

By: Frank Mao

Frank Mao — Tue, 14 Jul 2009 21:50:03 +0000

You might have those sr* in your ignore list, we don’t have this problem in our PB+SVN env.

By: galaxis

galaxis — Tue, 14 Jul 2009 18:25:57 +0000

SVN doesn’t store .sr* files unless you extract them yourself.

By: Henrique Bastos

Henrique Bastos — Fri, 29 Aug 2008 14:21:08 +0000

Those awfull revision increments while manipulation your PB source in SVN occurs because the source control adapter needs to control exclusive checkouts, and to do so it alters a svn property of the source file in the subversion repository. It really sucks.

Another lame problem that some SCC Proxies do is to increment the revision number for each file in a commit list.

Newer versions of PushOK SVNSCC uses the svn lock property that is not versioned, eliminating the revision increments. It also do multi-file commits correctly.

By: Rahul Jain

Rahul Jain — Fri, 26 Oct 2007 20:51:56 +0000

Download TortoiseSVN. It integrates with context menu on Windows Explorer. You will see Branch/tag as a menu when you right click on the folder where the SVN files are located. For PB, the .sr* files will be stored in the SVN, so you can go to the root where your PBLs are the tag that folder.

Hope this helps.