Hi Everyone,
I tested a check-out of 5.6.3 from version control. Its botched.
It looks like a drag/drop from a VMware guest to my OS X host got mangled.
There are about six or eight problems like these:
--- a/ecp.h
+++ b/ecp.h
@@ -143,6 +143,3 @@ private:
NAMESPACE_END
#endif
-E_END
-
-#endif
And:
--- a/seal.h
+++ b/seal.h
@@ -48,6 +48,3 @@ struct SEAL : public SEAL_Info<B>, public
SymmetricCipherDocumentation
NAMESPACE_END
#endif
-SPACE_END
-
-#endif
Notice the tail of the file has extra garbage.
This needs to be corrected before Monday morning. I think we have three
options:
(1) check-in the fix and call it 5.6.4
(2) ckeck-in the fix and call it 5.6.3
- re-tag check-in to CRYPTOPP_5_6_3
- rebuild ZIP to ensure consistent sources
(3) check-in the fix and do nothing
(3) is not a good option because it means folks who use CRYPTOPP_5_6_3 for
their release engineering have a broken set of sources.
Are there any other options? How should we proceed with it?
Jeff
--
--
You received this message because you are subscribed to the "Crypto++ Users"
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at
http://www.cryptopp.com.
---
You received this message because you are subscribed to the Google Groups
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
