[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Design Session notes: tool chain (and other) dependencies of our build and runtime system
- To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- From: Edwin Torok <edvin.torok@xxxxxxxxxx>
- Date: Thu, 22 Sep 2022 12:51:48 +0000
- Accept-language: en-GB, en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=EGfyu/UkZ7YBCwCZuNIYtIwDxlbwfmJsJou5ZhQvv/M=; b=gQ0jWibZbMTdNyhJUfNleyPCyaz0C/7iKtgOmWCTwZKTgGIDQtWVryZgy/QSxEoMO5GJYMkBYZapFjT+jLfAuoailUjY8RjMtrXdZFchB5h1AHESFMSNjzFgqoHog9aIU1RyRShNmdlv+kAK2aWeaQtORUTwJ35nG5mXpk7bsDqNuy/npR05aAYe22jDHEyvMcq3woIPKoiwlFBJ+lahj75yKSFYqUHjcsJIJsA+w+scLjne9sbO2l7UCCYA7YmaBxTYqdb72G2mevy66qHQZYV3A/8KKkGPjTyFYOIsBjCTskLgJSlzouEx9bfOUsyJbP0kQ0DgDBzBGEEyKvcEaQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=eU+DLPf7TUePc+5cpApbpE6DgWiEVJsdT+6oNAuBCeqK3xbVelRkrNemJK06G1flSCC1o3BnOKQFqlXVRv+Nvm7AQc+Z1eWdvFy6hnNm6hnbxsI2rM2p/qsYgccAlr1dpWMntlOtczesrLDxCGehEQr2Wc3qMi7OdnqM5+t39upUzEiNj9q1YJvJKA++wi1U2cFAZfHMAW2eDlHIHy6BhRdvaKYGz5dirT6jWxhK7zo8iL9F8tRLvEwhUpBsBMKuD2lkrECEvuYkFw1mSMQpMOHyq7A5t4wDRAGpeUqwFOVK8an34Yhk8BbAibKwL+eOppM986x6WNB1dLXU5QC19Q==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=citrix.com;
- Delivery-date: Thu, 22 Sep 2022 12:52:14 +0000
- Ironport-data: A9a23:zUOv6Kve3Tni77HLYBZ1UUhy7ufnVClfMUV32f8akzHdYApBsoF/q tZmKTyOM6mKYmP2c9B+ati+908HsZTQzYAxTVRk+yA8HysS+JbJXdiXEBz9bniYRiHhoOOLz Cm8hv3odp1coqr0/0/1WlTZhSAgk/vOHtIQMcacUghpXwhoVSw9vhxqnu89k+ZAjMOwRgiAo rsemeWGULOe82MyYzl8B56r8ks15qyj4mlA5DTSWNgQ1LPgvyhNZH4gDfnZw0vQGuF8AuO8T uDf+7C1lkuxE8AFU47Nfh7TKyXmc5aKVeS8oiM+t5uK23CukhcawKcjXMfwXG8M49m/c3Kd/ /0W3XC4YV9B0qQhA43xWTEAe811FfUuFLMqvRFTGCFcpqHLWyKE/hlgMK05FYMe5ct1GTFtz L8ndmwqShOIm72PzpvuH4GAhux7RCXqFKU2nyg6iBv/XbMhS52FRLjW79hF2jt2ntpJAfvVe 8seb3xocQjEZBpMfFwQDfrSns/x3iW5L2Ie9Q/T/PVui4TQ5FUZPLzFPdbLe9rMWcJPmUWwr WPa5WXpRBodMbRzzBLVqyv03LSUwUsXXqpKKpKnrM5Eh2bD31IyAzhIfnW7oMSQ3xvWt9V3b hZ8FjAVhbg/8gmnQ8fwWzW8oWWYpVgMVtxICeo45QqRjK3O7G6k6nMsSzdAbJkssp8wTDlzj FuRxYq2XHporaGfTm+b+vGMtzSuNCMJLGgEIygZUQ8C5Nqlq4Y25v7Scute/GeOpoWdMVnNL /qi8EDSW517YRY36piG
- Ironport-hdrordr: A9a23:Y3w9/akNioCTkOCpjKwGpc8J0ajpDfOcimdD5ihNYBxZY6Wkfp +V8cjzhCWftN9OYhodcIi7Sc+9qeu1z+883WBjB8baYOCAghriEGgC1/qq/9SEIUHDH4FmpM NdmsRFaeEYbmIKx/oSgjPIdOrIqePvmM/HuQ609QYPcegeUdAE0+4PMHf4LqQZfml7LKt8MK DZyttMpjKmd3hSRN+8HGM5U+/KoMCOvI76YDYdbiRXpDWmvHeN0vrXAhKY1hARX3dk2rE561 XIlAT/++GKr+y78BnBzGXehq4m1+cJi+EzSvBkuPJlagkEuTzYJ7iJnIfy/gzdldvfqWrCVu O85ivIcf4Dr085NVvF2ScFkzOQqwrGrUWShGNwyEGT3PDRVXY0DdFMipledQac4008vMtk2K YOxG6BsYFLZCmw6BgUd7DzJmtXf2eP0AgfeNQo/glieJpbbKUUoZ0U/UtTHptFFCXm6Jo/GO 0rCM3H/v5ZfV6Tcnic5wBUsaqRd2V2Gg3DTlkJu8ST3TQTlHdlz1EAzMhamnsb7poyR5RN+u yBOKV1k7NFSNMQcMtGdZA8aNryDnaITQPHMWqUL1iiHKYbO2jVo5qy+7kx7PHCQu168HLzou WwbLp1jx9NR6u1M7zz4HRiyGGzfEytGTLw18pZ+591/rXhWbuDC1zzdGwT
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
- Thread-index: AQHYzoIUneM8XWvFi0qNsSgpxIUjbA==
- Thread-topic: Design Session notes: tool chain (and other) dependencies of our build and runtime system
Hi,
These are the raw notes for this design session from the Xen Summit:
https://design-sessions.xenproject.org/uid/discussion/disc_JEWVIhuv2TRAo2AXAZnP/view
Dependencies haven't been updated in quite some time:
* Toolchain
* system libraries, and other runtime deps
E.g. when to drop Python2.
Testing on old hardware might need it. Old hardware is difficult to keep
running,
e.g. older than N years.
Vendors may not support it anymore, but that is a separate discussion.
What distros for newest versions of Xen, as minimum?
Minor releases keep working.
Next release can make another choice. Not necessarily actively break, but
support might be best-effort.
Support old guests of course, but what about build?
Might limit testing on old hardware, if it is difficult to get new distros
running on it.
E.g. after announcing new release, announce set of distros for master.
Update list at least once in release cycle.
make change for 4.18.
Accept nominations of distros from community for consideration, and then take
decision.
Or perhaps use backport (e.g. EPEL).
Distros which have support policy (i.e. they say how long a particular release
is supported).
Can't test everything on all distros, might be package version based. E.g. GCC
>= version
CI testing vs do we want to fix the breakage or not even if we can't detect in
CI
Informal survey on xen-users, resend patch on xen-devel (perhaps survey if lots
of concerns raised)
Distro packages, even if not available by default.
Might be helpful: repology.org for checking versions
|
