The way I see most groups doing this is have the release be a ZIP file with the license and release notes. We shouldn't make it harder than that.
Nobody will open a hex editor to view a read me. The ext info in the filesystem is generally limited to 256 characters (or 512 in newer os's) including signature. -Nick On Jun 12, 2015 11:41 PM, "Alex Harui" <aha...@adobe.com> wrote: > I grabbed the EXE off the CI server. The Hex Editor I have can’t find the > LICENSE by examining the EXE file. My understanding from Roy was that’s > how most folks are going to look, so I’m not sure if this approach is > going to work. It might be that the LICENSE is compressed and thus not > discoverable. > > I’m going to poke around to see if the AIR package can stick plain text in > the .EXE. > > -Alex > > On 6/12/15, 9:24 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: > > >Hi, > > > >> Okay, I just pushed a change the build script that includes the LICENSE > >>and > >> NOTICE files along with the installation exe/dmg. These files would > >>end up > >> in the installation directory. I think this is sufficient, right? > > > >Partly. The LICENSE and NOTICE files need to reflect the contents of the > >binary as per [1]. This means the LICENSE / NOTICE files are different > >for the source release and the binary as different bits are included. I > >can help out with that. > > > >Thanks, > >Justin > > > >1. http://www.apache.org/dev/licensing-howto.html > >
