-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat:add deepin distribution #3253
base: main
Are you sure you want to change the base?
Conversation
Description: Log:
if ( | ||
d | ||
in { | ||
Distribution.debian, | ||
Distribution.deepin, | ||
Distribution.ubuntu, | ||
Distribution.kali, | ||
} | ||
and version_codename | ||
): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please don't change this if it is not needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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?
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. :)