Re: Debian security / porting support and embedded codebases
- To: adrelanos <email@example.com>
- Cc: firstname.lastname@example.org, email@example.com
- Subject: Re: Debian security / porting support and embedded codebases
- From: intrigeri <firstname.lastname@example.org>
- Date: Sat, 09 Mar 2013 17:43:42 +0100
- Message-id: <[🔎] email@example.com>
- In-reply-to: <512CC2E5.firstname.lastname@example.org> (email@example.com's message of "Tue, 26 Feb 2013 14:12:53 +0000")
- References: <CAMtFrUFzOvMk7vWr_gB+R94hhEvOGSuTNaAe_Zia6oxwPZQzMw@mail.gmail.com> <firstname.lastname@example.org> <CAHsXYDC=br0n8ymddRZkdZyxOegg1xenOg-P6h3sJkwTAA5GLA@mail.gmail.com> <512BD2FF.email@example.com> <firstname.lastname@example.org> <512CA23B.email@example.com> <firstname.lastname@example.org> <512CC2E5.email@example.com>
adrelanos wrote (26 Feb 2013 14:12:53 GMT) :
> Tails developers:
> How frequent are requests for armel, armhf, arm64, mips, mipsel, sparc,
> powerpc, Hurd ports?
(Tails developer hat on.)
Here we go:
- arm*: quite a lot already, and I expect to see this grow seriously
in the future as ARM -based laptops, tablets etc. get more and
- powerpc: quite a lot until roughly two years ago, less and less
- others: none that I remember.
But obviously, Tails has a quite specific set of usecases and a quite
small userbase, so the fact nobody went as far as asking Tails
developers about support for another architecture certainly does not
imply that nobody is interested in running Debian (and, why not,
random software we ship, or may ship, in Debian) on it.
>> make it fully portable or there
>> is no point considering inclusion in Debian.
(Debian developer hat on.)
I would be surprised if the Torbrowser patches made Iceweasel any less
portable. It could be useful to confirm this, e.g. by building Tails'
Iceweasel + Torbrowser source package  on Debian architectures not
supported by the Tor project. Oh, here's yet another way to help :)
> The point is: people are interested in anonymous browsers - there
> are none in Debian.
As mentionned about every time this situation is mentioned: there's
a plan that has got the agreement of the people who would be the most
impacted by the code duplication (namely: the Iceweasel maintainer and
the security team). Nobody had time to implement this plan or design
a better one yet. Anyone interested in *fixing* this situation should
go talk to Jérémy Bobbio <firstname.lastname@example.org>.
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc