View Single Post
Old 10-05-2022, 12:20 PM   #15
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,884
Karma: 6120478
Join Date: Nov 2009
Device: many
From studying the dulwich code, direct manipulation of the message field of the object is not possible as the message forms part of the data that is hashed to create its id which is how the proper file is found.

Even tag_delete does not remove that annotated tag objects hash file, it just deletes the reference to it.

So changing an annotated tag message field directly is not possible, and using tag_delete and tag_create will just leave orphaned hash files in the repo.

Perhaps expanding the role of the .bookinfo file to keep a tag description for every tag is the right way to go here.
KevinH is online now   Reply With Quote