[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: why package Signal in Debian? (was Re: Bug#1113746: ITP: node-noop6 -- No operation as a module using an arrow function)





Le mar. 2 sept. 2025 à 23:07, Josh Triplett <josh@joshtriplett.org> a écrit :
Jonathan Dowland wrote:
> On Tue Sep 2, 2025 at 3:23 AM BST, Sergio Durigan Junior wrote:
> > This package will be maintained by the Debian _javascript_ team.  It's a
> > requirement for signal-desktop.
>
> I use and value Signal, but what's the point of packaging
> signal-desktop in Debian? Surely the packaged client will perennially
> be too out-of-date to connect to the servers. Certainly by the time it
> reaches a stable release.

Speaking only as a user here: I'd *love* to see signal-desktop packaged
in Debian. It wouldn't help stable anytime soon[1], but it'd work well
in experimental or perma-unstable.

The upstream signal Debian packages install to `/opt/Signal`, and bundle
various things, including their own copy of electron, ffmpeg, GL/Vulkan
libraries, etc. WOuld be nice to have something closer to Debian Policy.

[1] Unless it's possible to eventually adopt procedures similar to what
Firefox follows to get new releases into stable, but that's the kind of
long-term effort that would *follow* having a well-established package
in experimental or perma-unstable-with-standing-serious-bug.

Let's try to get electron first... 

Reply to: