From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: Postman
Date: Thu, 06 Jul 2023 21:46:31 +0200 [thread overview]
Message-ID: <20230706194631.842xeINuRpVpWL0twi3JqFpwSNaGC-j0ZKR9mL7wZZ8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12168@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/12168#issuecomment-1624218959
Comment:
> Why the "electron" label with a sick emoji? Are Electron apps banned from Void?
They are usually not easily packagable, most PRs that never get merged for electron apps just repackage binaries for x86_64+glibc, which is not acceptable for multiple reasons. Rerpacking binaries for open source software is bad practice and especially bad for things like electron which has a ton of dependencies, that would potentially lock our repository to a specific version that we can't update until the binaries are rebuild by upstream.
Getting electron packages to work with the system electron packages we have requires some work and the people mostly interested in electron packages are generally more concerned about using a program than packaging and maintaining it.
The emoji has a longer history, it was added before we had packaged system wide electron packages, which would either require to package the binaries or compile an electron app for 8+ hours from source, which is not feasible.
next prev parent reply other threads:[~2023-07-06 19:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 16:17 [ISSUE] " voidlinux-github
2021-03-20 0:43 ` LVKILL
2021-03-20 0:44 ` LVKILL
2021-03-20 0:45 ` LVKILL
2023-02-03 5:44 ` sistematico
2023-07-06 16:02 ` hholst80
2023-07-06 19:42 ` Duncaen
2023-07-06 19:43 ` Duncaen
2023-07-06 19:44 ` Duncaen
2023-07-06 19:46 ` Duncaen [this message]
2023-07-06 19:47 ` Duncaen
2023-07-06 19:48 ` Duncaen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230706194631.842xeINuRpVpWL0twi3JqFpwSNaGC-j0ZKR9mL7wZZ8@z \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).