Re: CRYPTOPP_VERSION has reached its limits
Colin Brown <[email protected]> Tue, 28 Oct 2025 12:41:22 -0700 (PDT)
| Newsgroups | gmane.comp.encryption.cryptopp |
|---|---|
| Message-ID | <[email protected]> |
------=_Part_5386_1728613284.1761680482051 Content-Type: multipart/alternative; boundary="----=_Part_5387_1693818752.1761680482051" ------=_Part_5387_1693818752.1761680482051 Content-Type: text/plain; charset="UTF-8" G'day, Since we need to rewrite the version parsing code anyway, I'd like to suggest switching to calendar versioning for a permanent fix. The current system breaks at version 8.10.0. Any fix (hex, 4-digits, etc.) just delays the problem. Calendar versioning solves it forever: - Never breaks (works until year 9999) - Shows when released (2025.10 vs 8.9) - Used by Ubuntu, TeX Live, Cloudflare and other stable projects Same effort, we have to rewrite the parsing logic no matter what solution is picked This permanently fixes the versioning limit while making versions more meaningful. Happy to help implement if there's interest. On Monday, 2 October 2023 at 07:12:30 UTC+13 Jeffrey Walton wrote: > Hi Everyone, > > It appears CRYPTOPP_VERSION has reached its limits. We cannot express > Crypto++ 8.10 in the existing CRYPTOPP_VERSION format. > > I think we may need to make each part 2 digits. I.e., 081000. > > Please comment at https://github.com/weidai11/cryptopp/issues/1239. > > Jeff > -- 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/cryptopp-users/d31c852e-e242-4b09-8916-db7b9a8fe03dn%40googlegroups.com. ------=_Part_5387_1693818752.1761680482051 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <p dir=3D"auto" style=3D"box-sizing: border-box; margin-bottom: 16px; color= : rgb(31, 35, 40); font-family: -apple-system, BlinkMacSystemFont, "Se= goe UI", "Noto Sans", Helvetica, Arial, sans-serif, "Ap= ple Color Emoji", "Segoe UI Emoji"; margin-top: 0px;">G'day,= <br /><br />Since we need to rewrite the version parsing code anyway, I'd l= ike to suggest switching to calendar versioning for a permanent fix.<br sty= le=3D"box-sizing: border-box;" />The current system breaks at version 8.10.= 0. Any fix (hex, 4-digits, etc.) just delays the problem.<br style=3D"box-s= izing: border-box;" />Calendar versioning solves it forever:</p><ul dir=3D"= auto" style=3D"box-sizing: border-box; padding-left: 2em; margin-top: 0px; = margin-bottom: 16px; color: rgb(31, 35, 40); font-family: -apple-system, Bl= inkMacSystemFont, "Segoe UI", "Noto Sans", Helvetica, A= rial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji"= ;"><li style=3D"box-sizing: border-box;">Never breaks (works until year 999= 9)</li><li style=3D"box-sizing: border-box; margin-top: 0.25em;">Shows when= released (2025.10 vs 8.9)</li><li style=3D"box-sizing: border-box; margin-= top: 0.25em;">Used by Ubuntu, TeX Live, Cloudflare and other stable project= s</li></ul><p dir=3D"auto" style=3D"box-sizing: border-box; margin-top: 0px= ; margin-bottom: 16px; color: rgb(31, 35, 40); font-family: -apple-system, = BlinkMacSystemFont, "Segoe UI", "Noto Sans", Helvetica,= Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji&quo= t;;">Same effort, we have to rewrite the parsing logic no matter what solut= ion is picked</p><p dir=3D"auto" style=3D"box-sizing: border-box; margin-to= p: 0px; color: rgb(31, 35, 40); font-family: -apple-system, BlinkMacSystemF= ont, "Segoe UI", "Noto Sans", Helvetica, Arial, sans-se= rif, "Apple Color Emoji", "Segoe UI Emoji"; margin-bott= om: 0px;">This permanently fixes the versioning limit while making versions= more meaningful.=C2=A0</p><p dir=3D"auto" style=3D"box-sizing: border-box;= margin-top: 0px; color: rgb(31, 35, 40); font-family: -apple-system, Blink= MacSystemFont, "Segoe UI", "Noto Sans", Helvetica, Aria= l, sans-serif, "Apple Color Emoji", "Segoe UI Emoji"; m= argin-bottom: 0px;">Happy to help implement if there's interest.</p><br /><= div class=3D"gmail_quote"><div dir=3D"auto" class=3D"gmail_attr">On Monday,= 2 October 2023 at 07:12:30 UTC+13 Jeffrey Walton wrote:<br/></div><blockqu= ote class=3D"gmail_quote" style=3D"margin: 0 0 0 0.8ex; border-left: 1px so= lid rgb(204, 204, 204); padding-left: 1ex;"><div>Hi Everyone,</div><div><br= ></div><div>It appears <span>CRYPTOPP_VERSION has reached its limits. We ca= nnot express Crypto++ 8.10 in the existing </span><span>CRYPTOPP_VERSION fo= rmat.<br></span></div><div><br></div><div>I think we may need to make each = part 2 digits. I.e., 081000.<br></div><div><br></div><div>Please comment at= <a href=3D"https://github.com/weidai11/cryptopp/issues/1239" rel=3D"nofoll= ow" target=3D"_blank" data-saferedirecturl=3D"https://www.google.com/url?hl= =3Den-GB&q=3Dhttps://github.com/weidai11/cryptopp/issues/1239&sourc= e=3Dgmail&ust=3D1761766795637000&usg=3DAOvVaw16_iwXR65Ccmh3Jy9Vg1Yo= ">https://github.com/weidai11/cryptopp/issues/1239</a>.</div><div><br></div= ><div>Jeff</div></blockquote></div> <p></p> -- <br /> You received this message because you are subscribed to the Google Groups &= quot;Crypto++ Users" group.<br /> To unsubscribe from this group and stop receiving emails from it, send an e= mail to <a href=3D"mailto:[email protected]">cryp= [email protected]</a>.<br /> To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/= cryptopp-users/d31c852e-e242-4b09-8916-db7b9a8fe03dn%40googlegroups.com?utm= _medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/cryp= topp-users/d31c852e-e242-4b09-8916-db7b9a8fe03dn%40googlegroups.com</a>.<br= /> ------=_Part_5387_1693818752.1761680482051-- ------=_Part_5386_1728613284.1761680482051--