We have a new architecture , We have compiled a lot of packages.Now the system can work normally .
We want to submit to debian like RISC-V. Please What documents(or others) can we refer to.
I want to know the submission process and documents.I know RISC-V has done it ,but I do not know how to begain and what can referance.
Please help me . thank you !!!
2021/5/11 10:30:28 +0000，Debian开发人员 Paul Wise firstname.lastname@example.org 首先给出了回应：
I think you are talking about LoongArch? I read that CPUs supporting
it can also run MIPS, ARM, RISC-V and x86 binaries. Are there any
advantages to a new port instead of the existing binaries?
I would suggest to read the PortTemplate wiki page. Each item on it
should be completed for LoongArch to eventually become a viable Debian
port. Once you have read through it, followed each of the links and
you know the new Debian architecture names for LoongArch, you can
create new wiki pages for each of the architectures, then fill out the
template as you complete each item. Currently only the ia64 wiki page
was organised like this, other architecture wiki pages grew
2021/5/11 12:36:42 +0200，另一位 Debian 开发人员 Helmut Grohne email@example.com 给出了他的建议：
I think that recent port bootstrapping efforts have been performed using
HelmutGrohne/rebootstrap - Debian Wiki.
Please follow up on this email thread with the following information:
- What is the gnu triplet used for the port?
- How many bits? Endianess?
- What is the state of binutils support?
- What is the state of gcc support?
- What is the state of linux support?
- What is the state of glibc support?
- Do you have a preferred architecture name already?
When describing “what is the state of … support?”, please tell:
- If the support is upstreamed, since which version?
- If not, are patches posted? Where?
- If not, is support implemented in some fork? Where?
Once we got answers to all these, I suppose that extending rebootstrap
to support your architecture is the next step. Once finished, you get to
manually fill in the gaps and roughly end up with something close to
build-essential. Using that, you’ll set up a native build system and
build the rest of the archive. In the process, you’ll break build
dependency cycles using various means. The most common ones are nocheck
builds and cross compilation.
If you do irc, join #debian-bootstrap on oftc. Cross-bootstrap related
matters are best directed at firstname.lastname@example.org.