feat:add deepin distribution #3253
Conversation
Description: Log:
| if ( | ||
| d | ||
| in { | ||
| Distribution.debian, | ||
| Distribution.deepin, | ||
| Distribution.ubuntu, | ||
| Distribution.kali, | ||
| } | ||
| and version_codename | ||
| ): |
There was a problem hiding this comment.
| if ( | |
| d | |
| in { | |
| Distribution.debian, | |
| Distribution.deepin, | |
| Distribution.ubuntu, | |
| Distribution.kali, | |
| } | |
| and version_codename | |
| ): | |
| if d and d.is_apt_distribution() and version_codename: |
| def detect_distribution( | ||
| root: Path = Path("/"), | ||
| ) -> tuple[Optional[Distribution], Optional[str]]: |
There was a problem hiding this comment.
Please don't change this if it is not needed.
There was a problem hiding this comment.
Please don't change this if it is not needed.
Okay , I will modify this .
But I got a problem now. The build image.raw cannot be started by qemu. I am still trying to fix this problem.
There was a problem hiding this comment.
This copies the debian.py quite fully, which would be a maintenance burden long term. Can you have a look at kali.py for a pointer how to implement a Debian derivative?
There was a problem hiding this comment.
Thank you for your reminder . The current v20 and v23 are based on Debian, but the next version has many incompatibilities with Debian. Therefore, it was considered better to copy debian.py at the time.
After I fix the current qemu + oci issues, I will reevaluate how to use the kali.py methods to ensure compatibility with next versions.
Add deepin Root File System Creation with mkosi Support Starting from deepin v20 (Apricot).
Users can now utilize mkosi to build the root file systems for both deepin v20 (Apricot) and v23 (Beige). Here's how:
For deepin in v20 (Apricot):
For deepin v23 (Beige) specifically, with the repository mirror:
Sidenote: In accordance with the deepin branding guidelines, the preferred usage is to start the name "deepin" with a lowercase 'd', akin to how "openSUSE" begins with a lowercase 'o'. Therefore, in this context, we have intentionally used "deepin" rather than "Deepin"—this is not a typographical error. :)