Trouble understanding the patching system
by Isidore · in Torque Game Engine · 03/27/2003 (2:19 am) · 4 replies
Hello everybody!
I have a question about the torque patching sysyem.
I am not sure to understand it properly.
Are patchs to be integrated by the engine sooner or later?
I mean, I applied the TGEDayNight patch. Then if tomorrow another HEAD version is available, will it integrate this patch?
Or do I have to merge the TGEDayNight changes (or re-apply the patch?)
I checked the CVS change list and I couldn't find any reference to the day/night related stuff. I also read the patch guide, but I am still in the dark =/
I hope somebody can help me with this.
Cheers,
Isidore
I have a question about the torque patching sysyem.
I am not sure to understand it properly.
Are patchs to be integrated by the engine sooner or later?
I mean, I applied the TGEDayNight patch. Then if tomorrow another HEAD version is available, will it integrate this patch?
Or do I have to merge the TGEDayNight changes (or re-apply the patch?)
I checked the CVS change list and I couldn't find any reference to the day/night related stuff. I also read the patch guide, but I am still in the dark =/
I hope somebody can help me with this.
Cheers,
Isidore
#2
I mean, of course most resources won't end up in the HEAD. That is why they are usually described and given in terms of "lines to add" and "files to modify".
Which is usually enough to ensure a proper merging with later HEAD versions.
But the patch file will apply on a given HEAD. I mean, if one can today apply the patch, maybe tomorrow one won't be able, because the HEAD changed and the file version changed.
So, before right after applying a patch, is it necessary to list the changes manually in order to be able to maintain it for later versions?
If so, what is the purpose of using patch rather than resources? it seems far more complex and tedious to maintain doesn't it?
The logic I would expect would be that:
- resources won't probably get into the engine
- patchs will be integrated in the next HEAD.
But that might not be this simple (?_?)
Isidore
03/27/2003 (3:22 am)
yes, but TGEDayNight is a patch, not a resource isn't it?I mean, of course most resources won't end up in the HEAD. That is why they are usually described and given in terms of "lines to add" and "files to modify".
Which is usually enough to ensure a proper merging with later HEAD versions.
But the patch file will apply on a given HEAD. I mean, if one can today apply the patch, maybe tomorrow one won't be able, because the HEAD changed and the file version changed.
So, before right after applying a patch, is it necessary to list the changes manually in order to be able to maintain it for later versions?
If so, what is the purpose of using patch rather than resources? it seems far more complex and tedious to maintain doesn't it?
The logic I would expect would be that:
- resources won't probably get into the engine
- patchs will be integrated in the next HEAD.
But that might not be this simple (?_?)
Isidore
#3
If you want code checked in the head, you prepare a patch according to the [url="http://www.garagegames.com/docs/torque.sdk/gstarted/patches.html"]Submitting Patches[/url] document. Then you send the patch to a maintainer and request that the patch be integrated. Just putting it on the forums is not enough.
Just because a given resource is in patch format, does not mean that it was sent to GG for inclusion into the head.
Edit: fixed bad link
03/27/2003 (7:12 am)
Resources will very rarely be checked into the head, because the integrator (a GG staff member or associate) has to do find the resource then do all the integration work manually. If you want code checked in the head, you prepare a patch according to the [url="http://www.garagegames.com/docs/torque.sdk/gstarted/patches.html"]Submitting Patches[/url] document. Then you send the patch to a maintainer and request that the patch be integrated. Just putting it on the forums is not enough.
Just because a given resource is in patch format, does not mean that it was sent to GG for inclusion into the head.
Edit: fixed bad link
#4
Well, I think it is not a good idea to use a patch format for resources. Now I applied the patch, it will be bothering to maintain it with next HEADs =(.
I guess there is no other choice than check manually all the changes brought along with the patch...
Anyway, thanks for your reply John, I understand now :)
Cheers,
Isidore
03/28/2003 (12:23 am)
So that was the explanation. It was just a resource using the patch format...Well, I think it is not a good idea to use a patch format for resources. Now I applied the patch, it will be bothering to maintain it with next HEADs =(.
I guess there is no other choice than check manually all the changes brought along with the patch...
Anyway, thanks for your reply John, I understand now :)
Cheers,
Isidore
Torque Owner J. Donavan Stanley
Edit: Substituted resources for patches since that more accurate.