【官网】2019.5.19 CentOS8.0 最新进展

Contents

  1. CentOS 8 Rough Status Page

    1. General Steps
    2. Architectures
      1. Main architectures
      2. AltArch
    3. Current Timeline
      1. Definitions
https://wiki.centos.org/About/Building_8

centos8 还没准备好。。

CentOS 8 Rough Status Page

Red Hat Enterprise Linux 8 was released on 2019-05-07, and everyone is waiting to find out when the CentOS rebuild will occur. This document is meant to cover general questions and timeline for what is happening.

A CentOS major release takes a lot of planning and changes in tooling as it is based on a much newer version of Fedora than previous versions. This means that everything from the installer, packages, packaging, and build systems need major overhauls to work with the newer OS. This means that there is always a ramp up period depending on the changes needed to make a rebuild work. The differences between EL-8 and EL-7 are no exception as the kernel has changed drastically, the repository format has added ‘modules‘ and RPMS have grown many features that EL7 and before do not have. About the only item which has not drastically changed between EL7 and EL8 is the init system which is still systemd. [This is a first as EL5 had SysV, EL6 had Upstart, and EL7 had Systemd].

General Steps

Steps needed to make a CentOS rebuild usually follow these steps:

  1. Red Hat makes the sources available.

    1. This used to be done via src.rpms but 7 changed to git repos
    2. In 8 CentOS has partnered closer with Fedora and will be sharing git repos with the Fedora system
    3. The pushes from Red Hat started on 2019-05-07 and ended 2019-05-08
  2. CentOS needs to look at the sources and determine what is needed to build these packages
    1. The rpm format has added items like Suggests which change some tooling requirements
    2. The packaging format has moved from yum to dnf4/yum4 which added modularity. Modules are an additional hurdle because they allow parallel available versions of software but not parallel installability (aka you can build perl-5.24 and perl-5.26 and all perl modules need to be compiled against both sets.) Module stream versions are tied to certain timestamps which means you can‘t rebuild the RHEL or Fedora and get the exact same version name.
    3. There are always packaging loops which need to be worked out. You need golang-(X-1) to build golang-X but golang-(X-1) doesn‘t exist yet.. how do you build a version and break the loop?
  3. CentOS needs to set up a build system which can allow for these changes.
    1. While CentOS can use the Fedora build system as a template, there are items in it which don‘t make sense for CentOS.
    2. The EL-8 beta was useful but there are still major changes which need rethinking
  4. CentOS needs to go through the source code and find out all the places where debranding is needed.
    1. No you can‘t just "sed s‘/Red Hat/CentOS/‘ (someone always offers that)
    2. There are times when you do replace and times when you don‘t.
  5. Builds can start occurring through the system
    1. This usually requires a multi-loop as you do a build to get started
    2. Then rebuild that core with itself
    3. Then add some more and possibly repeat 1 && 2 a couple of times.
    4. Then you can start building out the rest of the packages
  6. The installer usually takes a certain amount of work to get packaged together.
    1. Some things need additional patches
    2. Some things just need to be ordered correctly
    3. Some things like shim signatures for Secure Boot take outside review by signing authority
  7. QA work can begin
    1. with testing of packages by themselves or building from them
    2. with installer testing for smoke tests
  8. Usually some sort of RC work is done
  9. A final build is released

The above is a ‘you asked the people trying to build the train when it will arrive‘ guide. That said, every release is different and the order and additional steps get found and added each time.

Architectures

Main architectures

The following arches are built automatically in parallel in our new Build System :

  • x86_64
  • ppc64le (Little Endian
  • aarch64 (ARM64, ARMv8)

Responsibility, Owner: CentOS Core SIG

AltArch

The following architecture (not existing upstream, so more difficult to boostrap) is also actually being worked, on, but mainly based on a combination of Fedora 27/28 pkgs that can be used to bootstrap the el8 beta rebuild and then iterating loops until we can include that architecture in our Koji Build System .

  • armhfp (ARM32, ARMv7 - aka armv7hl)

Responsibility, Owner : CentOS SIG-AltArch

Current Timeline


Item


Started


Ended


Status


Sources pushed to CentOS Git


2019-05-07


2019-05-08


DONE


Source code evaluation


2019-05-07


YYYY-MM-DD


Ongoing


New Build System Setup


2019-05-07


2019-05-08


DONE


Debranding patches added


2019-05-07


YYYY-MM-DD


Ongoing


Artwork Requested


2019-03-07


2019-05-07


DONE


Artwork Selections


2019-05-09


YYYY-MM-DD


Ongoing


Build Loop 0


2019-05-07


2019-05-??


Ongoing


Build Loop M


YYYY-MM-DD


YYYY-MM-DD


Not started


Build Loop N


YYYY-MM-DD


YYYY-MM-DD


Not started


Installer work


YYYY-MM-DD


YYYY-MM-DD


Not started


QA work


YYYY-MM-DD


YYYY-MM-DD


Not started


RC work


YYYY-MM-DD


YYYY-MM-DD


Not started


Release work


YYYY-MM-DD


YYYY-MM-DD


Not started

Definitions

  • DONE - Step is completed
  • Ongoing - Work is progressing
  • Not started - This step may requires work from another step to reach some completion or requires time from person who is working on other parts.
  • Build loop 0 - Getting an initial set of packages together which can then build more packages
  • Build loop 1 - Using the smallest set of packages to build a larger set which can then build more packages
  • Build loop N - I really don‘t know how many loops this is going to be.. so we will use N nomenclature.
  • Installer work - there are usually some work needed to make the installer actually work with various things like secure boot or different fonts or ‘oh they fixed that in an upgrade.img.. let us just short cut and put that here.‘

原文地址:https://www.cnblogs.com/jinanxiaolaohu/p/10888033.html

时间: 2024-11-05 11:34:04

【官网】2019.5.19 CentOS8.0 最新进展的相关文章

Opera官网打不开 下载Opera最新版本的实际地址

目前Opera官网可以打开,但是点下载时就会出错,国内无法访问Opera的下载地址,无法通过官网直接下载Opera浏览器.下面提供下载的方式. 一.通过官方的ftp站点下载 FTP地址为 http://ftp.opera.com/pub/opera/desktop/ 如图,选择合适的版本即可下载 虽然可以下载,不过下载速度有时候非常的慢,很坑爹. 二.通过快乐浏览站点下载 快乐浏览里定期更新主要浏览器的最新下载链接,通过此站点可以直接下载到最新的主流浏览器,当然包括Opera浏览器. 访问:快乐

vultr vps官网改版免费注册教程(最新优惠码)

本站强烈推荐的,国外超高性价比vps服务器Vultr官方网站最近更新了,导致一些朋友心生茫然,今天写个简易教程给大家. 首先是打开vultr官网,免费注册一个vultr账号.填写邮箱地址.密码,非常简单.如果你图安全,你还能开启两步验证功能,每次登录需要启用google authenticator验证码. 注册登录后台,可看左侧面板有一列功能栏,从上至下顺序分别是Servers服务器列表.Billing财务中心.Support客服中心.Affiliate推广.Account账户中心. 最常用的是

日益融合的德国工业4.0最新进展 ——2019年汉诺威工博会观感

本文作者:SAP全球高级副总裁.中国区总经理李强 融合是德国工业4.0不变的主题 自从德国政府在2013年汉诺威工博会上发布工业4.0概念以来,每一届汉诺威工博会的主题都被定格为「融合的工业(Integrated Industry)」,其差异反映在副标题的选择上.例如,2014年紧跟着的副标题是「未来趋势」,2015-2018年分别是「加入网络大家庭」.「发现解决方案」.「创造价值」.「连接与协作」,而到了2019年,则是「工业智能」.沿着这些副标题的发展脉络,我们可以充分了解作为全球工业4.0

● 进入文博会官网 - 2019北京(国际)文化产业博览交易会

展会介绍文博会顾名思义文化创意产业博览会,在京已经成功举办13届.上届文博会国际化程度大幅提高,共有5个国际组织.69个国家与地区的87个境外代表团组参加文博会活动,参展参会国家数量创历届文博会之最:全国18个省区市代表团参展参会.据不完全统计,本届文博会"文化创意产业重点项目签约仪式"上共签署文化创意产业项目39个,金额68.135亿元人民币. 2019北京文博会让我们必定再创辉煌!2019北京文博会举办时间05月29-06月01日!为期四天的展会带我们走进文博看世界,定位"

Android 7.0行为变化—开发者应该关注的(官网同步翻译)

Android 7.0行为变化-开发者应该关注的(官网同步翻译) 版权声明:转载必须注明本文转自严振杰的博客: http://blog.yanzhenjie.com 如果想了解更多Android7.0的内容,可以顺便再看看Android7.0写给开发者的一封信(官网同步翻译). 如果你的引文够好,推荐你阅读官网文章: Android 7.0 Behavior Changes Android N 除了提供诸多新特性和功能外,还对系统和 API 行为做出了各种变更.本文重点介绍你应该了解并在开发应用

如何在Maven官网下载历史版本

如何在Maven官网下载历史版本 历史版本一般会隔一段时间,便找不到,官网会及时显示的是最新版本.不多说,直接进入. https://archive.apache.org/dist/maven/binaries/ 成功在Maven官网里下载到历史版本! 其它,依次类推. 成功!

如何在Maven官网下载到历史版本

历史版本一般会隔一段时间,便找不到,官网会及时显示的是最新版本.不多说,直接进入. https://archive.apache.org/dist/maven/binaries/ 成功在Maven官网里下载到历史版本! 其它,依次类推.

python爬取银行名称和官网地址

爬取所有银行的银行名称和官网地址(如果没有官网就忽略),并写入数据库.目标网址:http://www.cbrc.gov.cn/chinese/jrjg/index.html(因为此网站做了反爬虫机制,所以这里需要我们将爬虫伪装浏览器进行访问.)关于爬虫伪装成浏览器访问可以参考这篇文章:https://blog.csdn.net/a877415861/article/details/79468878 话不多说直接上代码: import re from urllib import request f

最新版本MYSQL官网下载地址但是必须要注册后才能下载

因mysql5.0上执行函数不行,决定安装最新版本的mysql,在网上找了些绿色版的,安装总报1067错误,网上的各种方法都试了,就是不行,浪费时间不说,郁闷死了,最后决定去官网,官网上面有msi安装版和绿色版,必须注册下,才能进行下面的操作.因之前绿色版安装老报1067错,决定使用安装版,但是 进入到MSI下载页面(http://dev.mysql.com/downloads/installer/5.6.html) 发现没有X64关键字,没事,你把下图的第二个mysql-installer-w