developer/packaging/basics: 整修与补充 #84
Draft
+85
−91
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ruaharico
force-pushed
the
packaging-basics-feat-250224
branch
from
cc6c1d9 to
220a730
Compare
ruaharico
force-pushed
the
packaging-basics-feat-250224
branch
from
220a730 to
6ca7fd1
Compare
MingcongBai
requested changes
Mar 3, 2025
| @@ -187,14 +185,15 @@ SRCS="tbl::https://ftp.gnu.org/gnu/hello/hello-$VER.tar.gz" | |||
| CHKSUMS="sha256::8d99142afd92576f30b0cd7cb42a8dc6809998bc5d607d88761f512e26c7db20" | |||
| ``` | |||
|
|
|||
| 注意：我们在源码包 URL 中使用了 `$VER` 变量，这是个好习惯——因为这样一来，在更新软件包时就不需要再编辑 URL 了。 | |||
| 注意：我们在源码包 URL 中使用了 `$VER` 变量。为了保证可持续性，在 `spec` 文件中，源码包文件必须要有版本号。 | |||
There was a problem hiding this comment.
此处是跟《AOSC OS 软件包样式指南》的表述同步。
MingcongBai
requested changes
Mar 6, 2025
| @@ -187,14 +185,15 @@ SRCS="tbl::https://ftp.gnu.org/gnu/hello/hello-$VER.tar.gz" | |||
| CHKSUMS="sha256::8d99142afd92576f30b0cd7cb42a8dc6809998bc5d607d88761f512e26c7db20" | |||
| ``` | |||
|
|
|||
| 注意：我们在源码包 URL 中使用了 `$VER` 变量，这是个好习惯——因为这样一来，在更新软件包时就不需要再编辑 URL 了。 | |||
| 注意：我们在源码包 URL 中使用了 `$VER` 变量。为了保证可持续性，在 `spec` 文件中，源码包文件必须要有版本号。 | |||
|
|
||
| Don't worry about them for now, we will introduce them later. | ||
|
|
||
| # Release model | ||
|
|
||
| AOSC OS is maintained with a rolling release model. This means that there's no version number attached to a full AOSC OS release (similar to other rolling release Linux distros, like openSUSE Tumbleweed and Arch Linux). However, within the [aosc-os-abbs](https://github.com/AOSC-Dev/aosc-os-abbs) tree, there is a set of packages that constructs the [AOSC OS Core](https://github.com/AOSC-Dev/aosc-os-abbs/blob/stable/README.CORE.md), which consists of core runtime (the GNU C Library, etc.) and toolchains (GCC, etc.). This set of packages are updated in a versioned fashion (Core 7.0.1, 7.0.2, 7.1.1, etc.). | ||
|
|
||
| Thanks to the rolling model, there's only one update channel for the users - `stable`. When updating or introducing new packages, developers work on a separate branch in the tree (the aforementioned aosc-os-abbs), create a Pull Request about the modification, then upload the package built to a separate repository (parallel to the `stable` repository). Thus, the users may test the updated packages by using the [AOSC OS APT Topic Manager](https://github.com/AOSC-Dev/atm) (or ATM). Then, if the package is proven to be working, the pull request is merged and then the package is rebuilt against a clean `stable` environment, and pushed to the main repository. | ||
| Thanks to the rolling model, there's only one update channel for the users - `stable`. When updating or introducing new packages, developers work on a separate branch in the tree (the aforementioned aosc-os-abbs), create a Pull Request about the modification, then upload the package built to a separate repository and carry out tests. Thus, the users may test the updated packages by using `oma topics`. Then, if the package is proven to be working, the pull request is merged and then the package is rebuilt against a clean `stable` environment with automated tools, and pushed to the main repository. |
| @@ -36,17 +34,15 @@ The first thing is to install Ciel on the computer. On AOSC OS, just execute the | |||
|
|
|||
| Since Ciel manages standardised AOSC OS build environment (or the BuildKit), the build process does not have to happen on an AOSC OS machine. If you are using Arch Linux, you can install Ciel from AUR. | |||
|
|
|||
| Next, we will initialise and configure a Ciel workspace. `~/ciel` is used as a sample path for demonstration. **Note: Ciel needs to be run as `root` (you may use `sudo -i` to gain elevated permission).** | |||
| Next, we will initialise and configure a Ciel workspace. **Note: Ciel needs to be run as `root`.** You may use `sudo -i` to gain elevated permission, then the root shell will be entered, and the `~` will point to `/root`. You can also add `sudo` before each command (the corresponding directory of `~` will not change). | |||
There was a problem hiding this comment.
to gain a root shell and ~ will now point to...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.