Hi Jeffrey, Thanks for taking the time to answer. Please read below inline.
On 2017-02-14 03:53, Jeffrey Altman wrote: > They are built with WiX 3.9 scripts. The > installation packaging in the OpenAFS tree can no longer be used. I see. So I'll switch to a later version as Ben suggested and see what happens. Hopefully we won't have to reinvent the wheel. > As a reminder, the 1.7.3301 installers that AuriStor, Inc. distributes > > https://www.auristor.com/openafs/client-installer/ > > can be installed on Windows 10 and Windows Server 2016 because they are > grand-fathered. If the same sources were built today they would not > produce a working file system. This statement is a bit distrurbing. Do you mean that given the state of things, even if Windows buildbots start springing back to life and binaries for current OpenAFS versions become availble, no later version than the already built and signed 1.7.3301 can be installed on Win10 and later? Will Win7 be ok at least? Do you consider the whole effort to revive the Windows port is in vain? Or is there something the the Foundation is planning to do in order to move forward again on the Windows platform? Thanks, -K.
smime.p7s
Description: S/MIME Cryptographic Signature
