Source Code Access

vbo

New Member
Dec 27, 2025
3
0
36
did you read any of this post at all
I have. But i also leave open in my post that i don't have the full story, so no need for hostility. Specific to that post, it's just saying they had trouble with a public git repo before and decided not to do it with the new project (JS port) in favor of build flags and bundle management. But i don't know how the previous setup actually looked, or how they used it.

I used to do build management and it just seems like there've been solutions to this sort of thing for a while. It's totally the teams prerogative to adopt what works for them, but if they are actually looking for a solution, that's one of them.
 

Wafflesnake

Well-Known Member
Nov 4, 2023
710
301
I have. But i also leave open in my post that i don't have the full story, so no need for hostility. Specific to that post, it's just saying they had trouble with a public git repo before and decided not to do it with the new project (JS port) in favor of build flags and bundle management. But i don't know how the previous setup actually looked, or how they used it.

I used to do build management and it just seems like there've been solutions to this sort of thing for a while. It's totally the teams prerogative to adopt what works for them, but if they are actually looking for a solution, that's one of them.

seems to me like that's already been answered.
Which I'm not averse to potentially doing, but that means probably writing some shit to manage doing it - but I have five hundred other things to do, so that's "at some point in the distant future".
 

vbo

New Member
Dec 27, 2025
3
0
36
seems to me like that's already been answered.
From what i read, the post you're quoting outlines a different approach.

If someone on the team privy to how they're using git wants to answer that'd be interesting to read. I don't have any skin in this so it's no big deal though.
 

Wafflesnake

Well-Known Member
Nov 4, 2023
710
301
From what i read, the post you're quoting outlines a different approach.

If someone on the team privy to how they're using git wants to answer that'd be interesting to read. I don't have any skin in this so it's no big deal though.
no, i am quoting the fact that ged is aware and capable of doing things differently. its simply not a priority.
 
  • Like
Reactions: Nino

Calamity

Member
Aug 15, 2016
7
0
It's been 8 years at this point, though. Even for something that's low priority.. that's an awfully long time.
 

Nino

Well-Known Member
Jan 14, 2025
480
282
30
Jizzconsin
It's been 8 years at this point, though. Even for something that's low priority.. that's an awfully long time.
Low priority doesn't mean it will eventually be done. It means if literally anything comes up at all, that will likely be tackled first. And as anyone who's developed a game can tell you, there is Always something to be done.