rust 1.53.0 can't bootstrap rust 1.61.0 about solaris-userland HOT 5 OPEN

While we are planning on another CBE release, we don't have a schedule for it yet.

from solaris-userland.

Re: "Yes, the plan is for the binary packages built from the rust 1.61.0 bits you see in the git repository to be delivered in the Solaris 11.4.51 package repository."

Should we expect a new CBE release anytime soon? Current CBE still seems to be 11.4.42.111.0, and it's not cost-effective to pay for an Oracle support contract to get SRU releases for non-commercial hobbyist usage.

from solaris-userland.

Yes, the plan is for the binary packages built from the rust 1.61.0 bits you see in the git repository to be delivered in the Solaris 11.4.51 package repository.

from solaris-userland.

Thanks Alan, that's good news, I guess.

Since the binary package builds seem to be pretty slow in coming it sure would be nice if either (a) one could discern a date when new binary packages might be released, or (b) when things are committed to the git repository one could build them based on having built (or got the binary packages for...) the previous contents of the git repository. Having to wait for Oracle to build it all rather defeats the (perceived, from the outside) purpose of having the repository, doesn't it?

from solaris-userland.

I've worked forward from 1.53.0 to 1.57.0 by back-porting the patches from Userland's rust 1.61.0, using the generated manifests in place of the .p5m files, and building each release one step at a time.

The build process is disturbingly unreliable, as evidenced by the build script's "try it three times to see if it works" being hard-coded in, and actually observing it having to do this. The non-repeatability does not inspire great confidence in the system though I'm not sure if it's Solaris or Rust that is misbehaving.

from solaris-userland.