Re: Status of Debian on QNAP
On Wed, Nov 25, 2020 at 1:56 PM <email@example.com> wrote:
> other than open'n the door for folks what is involved in be'n a porter
Basically, take care of keeping the port useful for Debian users.
The following is advice for ports in general, I guess Adrian can
provide some info for armel in particular and the challenges it is
currently facing apart from the ones that started this thread.
The most important thing is to ensure it meets the requirements for
the next Debian stable release, at this stage it sounds like there
being enough registered porters is the main issue.
Next is to ensure that it meets the requirements for being on ftp.d.o
(rather than in ftp.ports.d.o) in general:
Next is to ensure it works on hardware that can't run armhf,
especially on devices where it is most commonly used by current users
and on new devices that can't run armhf. This mostly involves work on
bootloaders like u-boot, the Linux kernel and the Debian installer, as
well as web sleuthing to find out what pre-ARMv7 hardware still exists
in the market.
Next is to ensure the Debian installer builds and works:
Next is to ensure that as many packages as possible build and run on
armel and that package maintainers get the help they need resolving
Next is to ensure that the port is well-tested, currently armel does
not have support in the reproducible builds, DebCI or piuparts
Next is to maintain the documentation related to the port:
https://wiki.debian.org/Ports/armel (doesn't exist yet)
At some point it might be useful to have non-x86 live images, or
directly writable pre-installed images (almost the same thing).