From nobody Sun Jun 16 13:25:57 2024 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4W2DLB5KF3z5Nnv3 for ; Sun, 16 Jun 2024 13:26:10 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4W2DL95lKhz44Cd for ; Sun, 16 Jun 2024 13:26:09 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from kalamity.joker.local (123-1-21-232.area1b.commufa.jp [123.1.21.232]) (authenticated bits=0) by www121.sakura.ne.jp (8.17.1/8.17.1/[SAKURA-WEB]/20201212) with ESMTPA id 45GDPv3D021665; Sun, 16 Jun 2024 22:25:58 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dec.sakura.ne.jp; s=s2405; t=1718544359; bh=Fj2tCr6AL3tEvsIj1HHS45EnFBKWPZKnEe+atMJp6uk=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=t0ZYlFPnNTnty3k9kbWe6P3Qx0KGVLR7lafhBYf4u6kqmUGA5zNu3YeA0IF7eGAVz oH1NHwltp2HXLR/b2UUGT/8gQZ0gVzUyIVuIWq3CXrtLXpSb3u0kXCO0J/H12h8yyo Q/Pm4EO8Qb6MxxKZSYXnWtTrZa63gUTykB1Euepg= Date: Sun, 16 Jun 2024 22:25:57 +0900 From: Tomoaki AOKI To: ports@freebsd.org Cc: Daniel Engberg Subject: Re: Another berserker victim: 03b36d9 textproc/obsidian: Remove expired port Message-Id: <20240616222557.3ec65d1607af4cdd0d94293d@dec.sakura.ne.jp> In-Reply-To: References: Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP] X-Rspamd-Queue-Id: 4W2DL95lKhz44Cd On Sun, 16 Jun 2024 13:08:53 +0200 Daniel Engberg wrote: > On 2024-06-16T12:37:28.000+02:00, Gleb Popov > wrote: > > > This is partly my fault as a maintainer. We've updated Obsidian in our > >  > > $WORK tree, but I forgot to upstream it. > >  > > But I also agree that we should make an exception for Electron ports, because > >  > > - Electron itself is pretty fast-moving, but at the same time has a > >  > > lot of commercial consumers that aren't that keen for keeping up with > >  > > its pace > >  > > - We only have electron package building on the cluster, so it > >  > > wouldn't hurt package building side of things anyway. > >  > > What do you think, Rene? > > The thing is that they're very heavy, tends to accumulate CVEs quite > fast and have a lot of dependencies that we need to maintain (since > it's EoL upstream). We already have 4 versions in tree which is quite > a lot already.and likely quite time-consuming to maintain as it is. > >From what I can tell it also appears that almost every other distro > have dropped Electron 25 as it been EoL for 6 months already. > https://forumobsidian.md/t/electron-25-is-now-eol-please-upgrade-to-a-newer-version/72878 > > Given upstream's versioning I guess upstream recently started > supporting a more recent version as 1.6 was released about a week ago > and there's an alpha release using Electron 30. > > I do think the correct decision here was to remove it despite not > having a "fix" for all consumers though. > > Best regards, > > Daniel My guess is that most fatal problem about electron is that newer version does NOT assure building sources for old versions. Act just like C compilers does SHALL be how programming language processing system do. Even llvm/clang 18 can compile/link and run K&R sources. This is how SHALL be. If electron30 can build everything written in electron25 sanely, at worst with an option to specify language version, there should be no problems. No worries. Just switching BUILD_DEPENDS to the latest supported stable version (with modifying build options) is sufficient. If not, I can't call electron* as a proper programming language processing system. But for interpreters, preparing binaries for older version based on the latest code can be an option. -- Tomoaki AOKI