On Wed, Nov 25, 2015 at 10:32:06AM +0100, Jean-Pierre André wrote:
> Agreed. It should be plugin.h, but where should this be
> located ("src/plugin.h" ?)There are a few options I can think of: 1.) Make it include/ntfs-3g/plugin.h and install it with the library headers 2.) Make it src/plugin.h and require that compiling a ntfs-3g plugin requires access to the ntfs-3g source tree 3.) Make it src/plugin.h and install it as a separate "ntfs-3g-plugin-devel" package for plugin developers to use (3) sounds like "the right way", but for now I think it would be overkill to make a separate package just for that header. What do you think about (1) or (2)? > Microsoft advertises IO_REPARSE_TAG_WIM (0x80000008) > Is that not used for WIMBoot files ? No. IO_REPARSE_TAG_WIM is used to indicate a WIM image that has been "mounted" with ImageX or DISM, whereas IO_REPARSE_TAG_WOF with the "WIM provider" is used to indicate a single file whose data (specifically, the unnamed data stream) is stored in a resource in a WIM file. The former has been around since Windows Vista, whereas the latter was added in Windows 8.1 to support the "WIMBoot" feature. ------------------------------------------------------------------------------ _______________________________________________ ntfs-3g-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
