Format description for Patch files...

Message from Sean M Alderman via eLinkDoes anyone have any kind of documentation on how to build a patchfile? I've found a few instances when porting modules from the Builderto Unix where weird things happen that I can't reproduce in thebuilder. I had hoped to be able to write and put a patch in on the unixsystem that I can get some extra logging from.Thanks.-- Sean M. AldermanITRACK Systems AnalystPACE/NCI - NASA Glenn Research Center(216) 433-2795

Find more posts tagged with

Comments

eLink User

Message from Dylan Wright via eLinkThere is something for this in the customizationsRT module.-----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com] Sent: Monday, November 26, 2001 11:35 AMTo: eLink RecipientSubject: Format description for Patch files...Format description for Patch files...Posted by eLink on 11/26/2001 02:34 PMMessage from Sean M Alderman via eLinkDoes anyone have any kind of documentation on how to build a patch file?I've found a few instances when porting modules from the Builder to Unixwhere weird things happen that I can't reproduce in the builder. I hadhoped to be able to write and put a patch in on the unix system that Ican get some extra logging from.Thanks.-- Sean M. AldermanITRACK Systems AnalystPACE/NCI - NASA Glenn Research Center(216) 433-2795[To reply to this thread, use your normal e-mail reply function.]============================================================Discussion: Development Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=786303&objAction=viewLivelink Server: https://knowledge.opentext.com/knowledge/livelink.exe

John_Shoun

Open Text doesn't provide any documentation on the patch format to discourage it's use (this is probably a good idea since they can be high risk).But we don't let that stop us.We build patches if only a couple of methods need to be changed. More than that and we build a module.There is an easy way to create a patch however. Go into the builder and create a new ospace. Orphan the feature or object you want to change. Once this is done there is an undocumented operation that will save the new module as a patch file. (Look at the PATCH ospace and the DUMP function to see how this is done.)Be careful ...

eLink User

Message from magnus <<A HREF="mailto:magnus@ids.se">magnus@ids.se> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Agree I don't understand why OT is not explaining the format,.,,,.

I did some debugging on a site with Livelink Directory Service on monday and as they

didn't have the builder installed it was rather straight on to do a patch and add some extra logging info.

We solved the problem that was a maybe bug in Livelink Directory service and without

beeing able to print out why the module worked like it did we should not have found the

problem .....

One Vote for patch documentations ....

Magnus@ids.se

----- Original Message -----

From: eLink Discussion: Development Discussion

To: eLink Recipient

Sent: Monday, November 26, 2001 11:29 PM

Subject: patch documentation

patch documentation Posted by NortelNC Admin (Shoun, John) on 11/26/2001 05:22 PM
In reply to: Format description for Patch files... Posted by eLink on 11/26/2001 02:34 PM

Open Text doesn't provide any documentation on the patch format to discourage it's use (this is probably a good idea since they can be high risk).

But we don't let that stop us.

We build patches if only a couple of methods need to be changed. More than that and we build a module.

There is an easy way to create a patch however. Go into the builder and create a new ospace. Orphan the feature or object you want to change. Once this is done there is an undocumented operation that will save the new module as a patch file. (Look at the PATCH ospace and the DUMP function to see how this is done.)

Be careful ...

eLink User

Message from Sean M Alderman via eLinkI'll just put in a word of thanks to Hans Stoop for sending me a ratherquick description of how to make patches (despite the fact that I gavehim a hard time).I have a cgi that implements a web client to help me automate some tasksin livelink. I wrote a patch to determine that the reason it wasn'tworking had something to do with the database configuration...in that mydatabase userid had the wrong case.Anyway, the file that Hans sent me was labeled Chapter 13 - Creating apatch. I'd actually like to get my hands on the rest of the Chapters ofthe book this came from. So I'll vote not just for patch documentationbut for the source of the patch documentation.I also think it would be nice to see if there's a way that OT could makeit easier for module developers to create patches. Meaning that patcheshave to be of the format patXXXXX.txt where XXXXX is a number withleading 0's if necessary. Wouldn't it be cool if there was a differencebetween OT system patches and third party/custom module patch filenames? This way we'd never have the chance of overwriting an OT patchwith one of our own.eLink Discussion: Development Discussion wrote:> > ------------------------------------------------------------------------> Name: Message Body> Message Body Type: Hypertext Markup Language (text/html)> Encoding: base64-- Sean M. AldermanITRACK Systems AnalystPACE/NCI - NASA Glenn Research Center(216) 433-2795

Placeholder_Siemens_(sglcuser44c_-_(deleted))

I am also very interested in getting more information about patches (especially synthax and handling).

eLink User

Message from Dylan Wright via eLinkThat's a very cool idea! Separate patch files for 3rd party modulesmakes a lot of sense. Obviously there would have to be some kind ofcheck to make sure it would only override scripts within the 3rd partyospace. -----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com] Sent: Wednesday, November 28, 2001 6:49 AMTo: eLink RecipientSubject: Re Vote for free patch documentation Re Vote for free patch documentation Posted by eLink on 11/28/2001 09:48 AMMessage from Sean M Alderman via eLinkI'll just put in a word of thanks to Hans Stoop for sending me a ratherquick description of how to make patches (despite the fact that I gavehim a hard time).I have a cgi that implements a web client to help me automate some tasksin livelink. I wrote a patch to determine that the reason it wasn'tworking had something to do with the database configuration...in that mydatabase userid had the wrong case.Anyway, the file that Hans sent me was labeled Chapter 13 - Creating apatch. I'd actually like to get my hands on the rest of the Chapters ofthe book this came from. So I'll vote not just for patch documentationbut for the source of the patch documentation.I also think it would be nice to see if there's a way that OT could makeit easier for module developers to create patches. Meaning that patcheshave to be of the format patXXXXX.txt where XXXXX is a number withleading 0's if necessary. Wouldn't it be cool if there was a differencebetween OT system patches and third party/custom module patch filenames? This way we'd never have the chance of overwriting an OT patchwith one of our own.eLink Discussion: Development Discussion wrote:> >------------------------------------------------------------------------> Name: Message Body> Message Body Type: Hypertext Markup Language (text/html)> Encoding: base64-- Sean M. AldermanITRACK Systems AnalystPACE/NCI - NASA Glenn Research Center(216) 433-2795[To reply to this thread, use your normal e-mail reply function.]============================================================Topic: Format description for Patch files...https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2628866&objAction=viewDiscussion: Development Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=786303&objAction=viewLivelink Server: https://knowledge.opentext.com/knowledge/livelink.exe

eLink User

Message from magnus <<A HREF="mailto:magnus@ids.se">magnus@ids.se> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

I did a year ago an application for 9.0 where I extended the user profile.

I did that by register a callback for my fields....

I then realised that if the "standard" Livelink User profiles where updated then

it also called the CB so I could save my values BUT

if the "standard" fields where not updated then I didn't get the CB

==> I did in my module a override on the wrong code in LL 9.0

Now the customer has installed some extra modules and it has stopped working

my override it looks ok if you debug and I can see it loads my modul ...

Question How can you check who is overiding what in a production system .,...

Regards

magnus@ids.se

eLink User

Message from Dylan Wright via eLinkI think if you add a column to kuaf, you can use UAPI.ExSet which willbe handled correctly by the script responsible for your problems ($LLIAPI.UsersPkg.UserUpdate ).-----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com] Sent: Thursday, November 29, 2001 3:14 PMTo: eLink RecipientSubject: In the patch and override land

eLink User

Message from Dylan Wright via eLinkAs far as the finding the culprit in a production system, use windowsfile find to search the contents of all olls for the scriptname you'reoverriding.-----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com] Sent: Thursday, November 29, 2001 3:14 PMTo: eLink RecipientSubject: In the patch and override land

eLink User

Message from magnus <<A HREF="mailto:magnus@ids.se">magnus@ids.se> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Thanks for the tips. I will check

FYI we added a new table that joined with the KUAF. The new table together

with some fields ( not supported by Livelink Directory Service) is if possible

updated using LDAP ....

Regards

Magnus Salgo

magnus@ids.se

----- Original Message -----

From: eLink Discussion: Development Discussion

To: eLink Recipient

Sent: Friday, November 30, 2001 12:50 AM

Subject: RE In the patch and override land

RE In the patch and override land Posted by eLink on 11/29/2001 06:50 PM
In reply to: In the patch and override land Posted by eLink on 11/29/2001 06:13 PM

Message from Dylan Wright <dwright@novare.com> via eLink

I think if you add a column to kuaf, you can use UAPI.ExSet which will
be handled correctly by the script responsible for your problems (
$LLIAPI.UsersPkg.UserUpdate ).

-----Original Message-----
From: eLink Discussion: Development Discussion
[mailto:development@elinkkc.opentext.com]
Sent: Thursday, November 29, 2001 3:14 PM
To: eLink Recipient
Subject: In the patch and override land