Re: racket-vulkan, I'd like to have a version number that conveys which version of the Vulkan specification I'm tracking, as well as the version of the utilities I write surrounding it.
Per the docs for (valid-version?) and package metadata, it does not look like I can do this well. I'm not even seeing anything about specifying custom metadata. Is that in an entirely different part of the docs? Here are the options I see so far: - Smush the Vulkan spec version and my actual package version in a ‹maj›.‹min›.‹sub›.‹rel› string and come up with rules to extract both. - Version only the code in my package. Oblige people needing to upgrade to check if the spec version supported by the package has changed either by reading a changelog or calling a procedure in the upgraded package. Come up with rules re: what a Vulkan version change does to my package version. - Create a second package. I'm not crazy about any of these options, but am leaning towards the first since its the most friendly to deployment automation, has the smallest support commitment, and keeps the "one stop-shop" experience I'd want to provide. But is there a better way? ~slg -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/Lcb3ALbl9B3qhFlVSQVLzSBKhf1CLN8nrCH0TOcoHXmpP8o4CUqXDecUBeha7Y_q2f10sLRAkEnBsK1BUujNfDePXJy674nLoHn6Ad_HRMQ%3D%40sagegerard.com.
