[Tomcat76]

This is for existing addon makers to see if HFSLIP would support their addon or not.
Applies to HFSLIP 1.2.2 and newer.


HFSLIP fully supports/parses the following sections:
* txtsetup_files
* txtsetup_files_home
* txtsetup_fileflags
* txtsetup_dirs
* dosnet_files
* dosnet_files_home
* sysoc
* editfile
* filenames
* addprogram
* GuiRunOnce
* FileMove
* DirDelete

HFSLIP partially supports the following sections:
* txtsetup_files_pro (this is parsed for XP Pro but this doc says it's for any non-Home OS)
* dosnet_files_pro (same)

HFSLIP deliberately ignores the following sections:
* AddDirective (HFSLIP automatically creates section headers in destination files if they don't exist)
* svcpack_catalogs (catalog files are handled automatically by HFSLIP provided they exist in the SVCPACK folder)
* i386_compress (files are automatically compressed unless they exist uncompressed in the source except for files in the ASMS folder)
* obsolete (it is assumed the HFSLIP user knows which hotfixes are obsolete when they include an addon)

Unsupported sections:
* extrafileedits
* txtsetup_remove (might conflict with other features of HFSLIP)
* dosnet_remove (same)
* registry_addreg (same)
* registry_delreg (same)
* obsolete_files (same)
* ...

This post has been edited by Tomcat76: 10 January 2007 - 11:00 AM

[Kiki Burgh]

a more definitive guide then for everyone! thanks for this TC!
for the sake of cross-referencing, here are previous related topics:
Special features 3. Application addons
HFAAO - Application Addon packs, (version 60301 and higher)
Introducing support for update/addon packs
Add-ons Location
HFAAO FLODER NOT USED