On 29/06/2026 10:12, Rainer Emrich via Cygwin wrote:
Hi folks,
I'm interested in updating the rust package. We have rust 1.91.0 but
some python modules I'm interested in, especially nc_app_api need an up
to date rust version which is 1.96.0.
It would be very helpful indeed if you would do this!
(I feel kind of bad about publishing the rust package without having a
plan in place to update it, but me doing everything doesn't scale very
well).
I'm able to build rust 1.92.0 from rust 1.91.0 successfully, but there
are some questions.
To build a rust version you need the same version or the version before,
to build 1.96.0 you need version 1.95.0 for example, and so on. So we
would need 1.92.0, 1.93.0, 1.94.0 and 1.95.0 to build 1.96.0 in the end.
Huh. I had the impression that this constraint only applied to nightly,
not released versions, but it's entirely possible I'm mistaken.
So, how to organize this package wise? Some ideas and hints are really
welcome.
I guess the simplest way is to build and publish the intermediate
versions (which is probably also helpful if there's a regression, since
it can then be tracked down to a specific version).
Our process should be described at [1].
If you send a mail to the cygwin-apps list saying you'd like to adopt
the rust package and providing an ssh key, I'll get you hooked up.
(you need to subscribe to be able to post to that list, but you can turn
mail delivery off)
Thanks!
[1] https://cygwin.com/packaging-contributors-guide.html#adopt
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
