David Timms writes:
Other than that, mock is the answer, and what Fedora packagers use to test build packages for any version.
Looked into this, it does seem like mock is the answer. The only gotcha I see to this approach would be if the newer release's compiler/support libraries require code changes to the packages being bootstrapped.
The iterative cycle of trying a mock build, then figuring out what broke, fixing the code, and then launching a mock build again – based on experience, I'd say this will be much slower than just installing the new release, and then figuring out what's going on, in a live environment.
Life on the bleeding edge is much more exciting. And fast-paced.
Attachment:
pgpvDPaGeG9Lm.pgp
Description: PGP signature
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
