Re: how to convey package porting details?

2022-06-06 Thread Marco d'Itri
On Jun 06, Paul Wise wrote: > There are lots of packages that need porting to every new architecture > that comes along. There are others that don't require porting but > benefit in some way from porting to some aspect of the architecture. Is this really worth the effort, considering that probabl

Re: how to convey package porting details?

2022-06-06 Thread 肖盛文
在 2022/6/6 16:47, Marco d'Itri 写道: > Is this really worth the effort, considering that probably RISC-V is > going to be our last port for a very long time? Perhaps loongarch64 will the next port. https://wiki.debian.org/Ports/loongarch64 Some codes of loongarch64 had been added to upstream ke

Re: how to convey package porting details?

2022-06-06 Thread Adam Borowski
On Mon, Jun 06, 2022 at 10:47:38AM +0200, Marco d'Itri wrote: > On Jun 06, Paul Wise wrote: > > > There are lots of packages that need porting to every new architecture > > that comes along. There are others that don't require porting but > > benefit in some way from porting to some aspect of the

Re: how to convey package porting details?

2022-06-06 Thread Holger Levsen
On Mon, Jun 06, 2022 at 10:47:38AM +0200, Marco d'Itri wrote: > Is this really worth the effort, considering that probably RISC-V is > going to be our last port for a very long time? you mean like 640kb should be enough for everyone? :) -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(deb

Re: how to convey package porting details?

2022-06-06 Thread Paul Wise
On Mon, 2022-06-06 at 10:47 +0200, Marco d'Itri wrote: > Is this really worth the effort, considering that probably RISC-V is > going to be our last port for a very long time? There are at least two or three new architectures in the pipeline already. loongarch64 from Loongson was already mention

Re: how to convey package porting details?

2022-06-06 Thread Marco d'Itri
On Jun 06, Holger Levsen wrote: > > Is this really worth the effort, considering that probably RISC-V is > > going to be our last port for a very long time? > you mean like 640kb should be enough for everyone? :) More like "free ABI is eating the world". I do not see much future for the archite

Bug#1012408: ITP: mathjax-siunitx -- Extension for libjs-mathjax to suppourt siunitx

2022-06-06 Thread Georges Khaznadar
Package: wnpp Severity: wishlist Owner: Georges Khaznadar X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: mathjax-siunitx Version : 0.1 Upstream Author : Yves Delley * URL : https://github.com/burnpanck/MathJax-siunitx * Lice

Re: how to convey package porting details?

2022-06-06 Thread Paul Wise
On Mon, 2022-06-06 at 16:52 +0200, Marco d'Itri wrote: > Maybe the usual suspects which require significant porting work could > start documenting instructions for porters in debian/README.source. Thats a good start, but doesn't provide a standard way to find out which packages contain such instr