1. Roland Smith
  2. PowerBuilder
  3. Wednesday, 28 August 2024 01:00 AM UTC

One of my customers used one of my utilities to delete objects from a library. In the PB IDE, the GIT interface doesn't see any deletes needing to be committed.

With an SCC API based source control system, my utility performs a SccRemove. For GIT, it seems to not be doing anything.

I'm wondering what needs to be done in order for the PB IDE to recognize that there are file deletes needing to be committed.

Accepted Answer
Benjamin Gaesslein Accepted Answer Pending Moderation
  1. Wednesday, 28 August 2024 06:36 AM UTC
  2. PowerBuilder
  3. # Permalink

The object was deleted directly from the PBL? Afaik the file needs to be deleted from the respective ws_objects subfolder for the PBL because that's what git actually tracks. The PBL itself is just one large blob. I usually delete the file from ws_objects/path/to/my.pbl/ and then do a refresh in PB, which deletes missing files from the PBL itself. So deleting it from both the PBL and in the file system should let PB know that the file is gone. I'm not sure if the libgit component built into PB will detect this change, you'd have to try.

Comment
  1. David Peace (Powersoft)
  2. Thursday, 29 August 2024 16:03 PM UTC
I was going to say the same, GIT is managed by the source control files in the file system not the PBL. This is a fundamental shift in SCC from what we are used for and is why in PB2025 the PBL can be deleted altogether.



Unfortunately that will change Rolands SCC code completely, we have all enjoyed using that stuff but we will need to rethink what we are doing in future.
  1. Helpful
  1. Roland Smith
  2. Thursday, 29 August 2024 18:21 PM UTC
When my utility updates objects, it updates the source file under ws_objects and the object in the PBL. I just need to update it to delete the file when objects are deleted from a PBL.
  1. Helpful
There are no comments made yet.


There are replies in this question but you are not allowed to view the replies from this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.