New -append_partition pseudo partition_number "all" und pseudo type_code "revoke"

xorriso/xorriso.texi

@@ -50,7 +50,7 @@
 @c man .\" First parameter, NAME, should be all caps
 @c man .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
 @c man .\" other parameters are allowed: see man(7), man(1)
-@c man .TH XORRISO 1 "Version 1.5.7, Jun 07, 2023"
+@c man .TH XORRISO 1 "Version 1.5.7, Aug 07, 2023"
 @c man .\" Please adjust this date whenever revising the manpage.
 @c man .\"
 @c man .\" Some roff macros, for reference:
@@ -4145,10 +4145,12 @@ and to write the loaded system area content without alterations.
 @strong{discard} gives up the El Torito boot catalog and its boot images.
 regardless whether loaded from an ISO filesystem or defined by commands.
 Any BIOS or EFI related boot options get revoked.
-Nevertheless, loaded system area data stay valid. If desired, they have to be
-erased by
+Nevertheless, loaded system area data and the possibly defined appended
+partitions stay valid. If desired, they have to be erased by
 @*
  -boot_image any system_area=/dev/zero 
+@*
+ -append_partition all revoke -
 @*
 @strong{keep} keeps or copies El Torito boot images unaltered and writes a new catalog.
 @*
@@ -4169,23 +4171,49 @@ you do know that the images need no patching, use "any" "keep".
 @strong{replay} is a more modern version of "patch", which not only cares
 for existing El Torito boot equipment but also for the recognizable
 boot provisions in the System Area. It discards any existing -boot_image
-setting and executes the commands proposed by command -report_el_torito "cmd".
+setting including the system area and executes the commands proposed by
+command -report_el_torito "cmd".
 @*
 This action will only succeed if the file objects mentioned in the
 output of command -report_el_torito "cmd" are still available. Do not
 remove or rename boot image files after -indev.
 @*
-Drop unknown El Torito:  -boot_image "any" "discard"
-@*
-Maintain recognizable stuff:  -boot_image "any" "replay"
-@*
-El Torito only for GRUB:  -boot_image "grub" "patch"
-@*
-El Torito only for ISOLINUX:  -boot_image "isolinux" "patch"
+Out of historical reasons @strong{replay} does not revoke all possibly made
+-append_partition settings but only overwrites those for which the loaded
+ISO image provides candidates.
 @*
 @strong{show_status} will print what is known about the loaded boot images
 and their designated fate.
 @*
+Examples:
+@*
+Drop unknown El Torito:
+@*
+ -boot_image any discard
+@*
+Drop El Torito, system area, appended partitions:
+@*
+ -boot_image any discard
+@*
+ -boot_image any system_area=/dev/zero
+@*
+ -append_partition all revoke -
+@*
+Maintain recognizable stuff after revoking possibly made -append_partition
+settings to surely get only the partitions from the loaded ISO:
+@*
+ -append_partition all revoke -
+@*
+ -boot_image any replay
+@*
+Re-adjust El Torito only for GRUB:
+@*
+ -boot_image grub patch
+@*
+Re-adjust El Torito only for ISOLINUX:
+@*
+ -boot_image isolinux patch
+@*
 @sp 1
 
 A @strong{bootspec} is a word of the form name=value. It is used to describe
@@ -4609,10 +4637,9 @@ In APM, 48465300-0000-11AA-AA11-00306543ECAC will be mapped to partition
 type "Apple_HFS", any other to "Data".
 @*
 If some other command causes the production of GPT, then the appended
-partitions will be mentioned there too. 
+partitions will be mentioned there too. GPT can be forced by
 @*
-The disk_path must provide the necessary data bytes at commit time.
-An empty disk_path disables this feature for the given partition number.
+ -boot_image "any" "appended_part_as=gpt"
 @*
 @cindex SUN SPARC boot images, activation
 With SUN Disk Label (selected by -boot_image any sparc_label=):
@@ -4621,8 +4648,20 @@ partition_number may be 2 to 8. Number 1 will always be the ISO image.
 Partition start addresses are aligned to 320 KiB. The type_code does not
 matter. Submit 0x0.
 @*
-Partition image name "." causes the partition to become a copy of the next
+disk_path "." causes the partition to become a copy of the next
 lower valid one.
+@*
+With MBR, GPT, and SUN alike:
+@*
+The disk_path must provide the necessary data bytes at commit time.
+@*
+Issueing -append_partition with a partition number that was already used in
+a previous -append_partition command does not cause an error but silently
+overrides the previous setting.
+@*
+The pseudo type_code "revoke" or an empty disk_path prevent the partition from
+being appended. The pseudo partition number "all" may be used in this case to
+revoke all previous -append_partition settings.
 @end table
 @c man .TP
 @c man .B Jigdo Template Extraction: