From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: Android port of Emacs Date: Sat, 24 Jun 2023 15:57:55 +0200 Message-ID: <874jmx55ek.fsf@telefonica.net> References: <83v8fnslfz.fsf@gnu.org> <83edmask4z.fsf@gnu.org> <5c02371a-3c42-de66-70b7-4ed0d88cc3fa@gutov.dev> <87cz1td0ku.fsf@yahoo.com> <87cz1ta5fr.fsf@telefonica.net> <87edm645yy.fsf@yahoo.com> <878rc95a1t.fsf@telefonica.net> <87r0q1vwtl.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9294"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jun 24 15:59:13 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qD3nE-0002BZ-O0 for ged-emacs-devel@m.gmane-mx.org; Sat, 24 Jun 2023 15:59:12 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qD3mE-000668-Fd; Sat, 24 Jun 2023 09:58:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qD3mA-000658-VN for emacs-devel@gnu.org; Sat, 24 Jun 2023 09:58:06 -0400 Original-Received: from relayout03-redir.e.movistar.es ([86.109.101.203]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qD3m8-0006Yh-7t for emacs-devel@gnu.org; Sat, 24 Jun 2023 09:58:06 -0400 Original-Received: from sky (95.red-83-37-210.dynamicip.rima-tde.net [83.37.210.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: 981711563@telefonica.net) by relayout03.e.movistar.es (Postfix) with ESMTPSA id 4QpG0454jdzMmft; Sat, 24 Jun 2023 15:57:56 +0200 (CEST) In-Reply-To: <87r0q1vwtl.fsf@yahoo.com> (Po Lu's message of "Sat, 24 Jun 2023 21:01:10 +0800") X-TnetOut-Country: IP: 83.37.210.95 | Country: ES X-TnetOut-Information: AntiSPAM and AntiVIRUS on relayout03 X-TnetOut-MsgID: 4QpG0454jdzMmft.AAA21 X-TnetOut-SpamCheck: no es spam, clean X-TnetOut-From: ofv@wanadoo.es X-TnetOut-Watermark: 1688219877.85624@o572EogrzcVJeFL6Lp2RPA Received-SPF: softfail client-ip=86.109.101.203; envelope-from=ofv@wanadoo.es; helo=relayout03-redir.e.movistar.es X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:307181 Archived-At: Po Lu writes: > =C3=93scar Fuentes writes: > >> Building those binaries (and its dependencies) can be quite a chore. So >> let's reverse the relation: can your port be built (toggling some >> configure options, for instance) so it can be packaged as a regular >> Termux binary? Which means that when executed from Termux the user would >> have a "native" Android Emacs with access to all those external binaries >> distributed by Termux. > > No, but it can (right now) be packaged with the "shared user ID" set to > that of Termux. When installed along side a Termux build signed with > the same package signing key as Emacs, Emacs will be able to access > executable files installed by Termux. If I understand correctly, this means that you can't start Emacs from Termux, but a specially-built Emacs could be launched as any other Android app and then it could invoke Termux applications. Isn't the "installed alongside Termux" part a bit complicated? I mean, if it is not possible for Termux to build, package and install your port alongside their other packages, how the user could do that? > BTW, it is quite simple to build Termux packages: changing some > environment variables and running `build-bootstrap.sh' is sufficient to > generate the bootstrap archive, and dpkg can then be used to install the > rest. How is that different from Termux themselves building and distributing your port? OTOH, I know from experience that creating, hosting and maintaining a software distribution (and that would be what you are describing, IIUC) is quite a lot of work, even when the number of packages is small-ish (about 50-100 in my case, counting dependencies.) So having a "hands-off" method for installing Emacs along with other software packages is crucial for gaining a broad adoption. > Hope that helped. I'm progressing on my understanding, thank you.