From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Affiliation with ExpidusOS?
Date: Sat, 17 Jul 2021 13:37:53 +0200 [thread overview]
Message-ID: <20210717113753.T_JyjkqWHJ3qlO97_L26MHSvghNoP3SiG1jUAcG7Jac@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32019@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/32019#issuecomment-881884441
Comment:
Void already supports the Pinephone. Other devices would probably have only 1 user and might require some device specific packages (custom kernel, uboot, etc.), so including them in Void wouldn't make much sense (even the Pinephone kernel in repositories is old). Having those packages in a separate repository like what ExpidusOS does would make more sense, but:
* it should be transparent (not have huge commits touching multiple packages with commit message "fix")
* it should upstream changes where possible
There are people interested in Void on a Pinephone, I know at least about @jcgruenhage and me, git log will probably tell you more. I have some updated packages in my own repository (the pinephone kernel, phosh, squeekboard...), but I wasn't able to properly test them yet, so I didn't make a PR.
next prev parent reply other threads:[~2021-07-17 11:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 9:46 [ISSUE] " Anachron
2021-07-17 10:07 ` sgn
2021-07-17 10:07 ` [ISSUE] [CLOSED] " sgn
2021-07-17 10:08 ` sgn
2021-07-17 10:40 ` Anachron
2021-07-17 10:56 ` sgn
2021-07-17 11:37 ` paper42 [this message]
2021-07-17 17:23 ` RossComputerGuy
2021-08-23 19:17 ` Chocimier
2021-08-23 19:17 ` [ISSUE] [CLOSED] " Chocimier
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=20210717113753.T_JyjkqWHJ3qlO97_L26MHSvghNoP3SiG1jUAcG7Jac@z \
--to=paper42@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).