subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Becroft <djcbecr...@gmail.com>
Subject Re: SVN Subversion- object level checkout
Date Thu, 13 Jan 2011 07:39:21 GMT
On Thu, Jan 13, 2011 at 5:24 PM, <amit.sasmal@wipro.com> wrote:

> Hello Micheal,
>
> Thanks for your mail.
>
> We are using Tortoise SVN-1.6.7 alongwith Power Builder 11.5.
>
> We want to lock (check-out) the core power builder object from SVN so
> that only one user can modify the object for that time. For this case,
> If we want to open the workspace from the repository (SVN) we are
> getting the attached message.
>
> Please let us know the correct process for the Power Builder connectivty
> with the proper Tortoise SVN SCC version to lock the core PB object.
>
> Appreciate your quick help.
>
> Regards,
>

I'm guessing that .PBW file relies on the rest of the files in that
directory. You'll need to checkout that directory prior to opening.

Cheers,
Daniel B.


> Amit Sasmal.
> Wipro Technologies.
>
>
> -----Original Message-----
> From: Michael Diers [mailto:mdiers@elego.de]
> Sent: Wednesday, January 12, 2011 7:27 PM
> To: SOURAV ROY (WT01 - Manufacturing)
> Cc: users@subversion.apache.org; Sudip Datta (WT01 - Manufacturing);
> Pabitra Mallick (WT01 - Manufacturing); Avik Nandi (WT01 -
> Manufacturing); Amit Sasmal (WT01 - Manufacturing)
> Subject: Re: SVN Subversion- object level checkout
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2011-01-12 09:57, sourav.sroy@wipro.com wrote:
> [...]
> > We will use Tortoise SVN (Subversion) as version control system or SCM
>
> > tool for our project. We are facing an issue for which we would like
> > to get a solution.
> >
> > We are linking SVN to Powerbuilder 11.5. We are trying to checkout
> > files at object level. Every .pbl file, have many files inside. But
> > SVN is not able to checkout those individual files which are inside
> the pbl file.
> > So is there a way by which SVN can checkout those files which are
> > inside pbl.
> >
> > TortoiseSVN 1.6.7,  2010/01/22
> > Subversion 1.6.9
> [...]
>
> Sourav,
>
> you need to play by PowerBuilder's rules, I'm afraid. Trying to use
> TortoiseSVN or any other "plain" Subversion client for checkin/checkout
> will cause you grief.
>
> You can still use TortoiseSVN for other tasks, like browsing logs,
> tagging and branching.
>
> The IDE supports the SCC API, and you need to use a plug-in for the IDE
> that can drive Subversion via SCC. This will magically do the right
> thing with objects in PBLs. Note that SCC encourages a serialized
> workflow with reservation ("locking") of objects.
>
> We evaluated PushOK's product a couple of years ago; at the time, it
> proved a good fit for our customer's needs.
>
> http://stackoverflow.com/questions/1162141/is-there-a-viable-scc-integra
> tion-for-subversion<http://stackoverflow.com/questions/1162141/is-there-a-viable-scc-integra%0Ation-for-subversion>
>
> (Please upgrade to Subversion 1.6.15. Subversion 1.6.9 sports a number
> of bugs that have been fixed since its release.)
>
> - --
> Michael Diers, elego Software Solutions GmbH, http://www.elego.de
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (Cygwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk0ts0EACgkQcEKlWnqVgz0QngCfcTZ5gHe8upwsAH5x3zNZbFXB
> 6vEAn27V2eskpxWfOfh5Hyu6747LFZlg
> =jf++
> -----END PGP SIGNATURE-----
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any attachments to
> this message are intended for the exclusive use of the addressee(s) and may
> contain proprietary, confidential or privileged information. If you are not
> the intended recipient, you should not disseminate, distribute or copy this
> e-mail. Please notify the sender immediately and destroy all copies of this
> message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses. The
> company accepts no liability for any damage caused by any virus transmitted
> by this email.
>
> www.wipro.com
>

Mime
View raw message