Github messages for voidlinux
 help / color / mirror / Atom feed
From: JamiKettunen <JamiKettunen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: buffyboard-0.2.0
Date: Sun, 27 Feb 2022 21:57:08 +0100	[thread overview]
Message-ID: <20220227205708.5Ibsu9EgChzGb8hOkt6YXMfQQ4m_vpMQQdIr1FZnixQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35876@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 774 bytes --]

New comment by JamiKettunen on void-packages repository

https://github.com/void-linux/void-packages/pull/35876#issuecomment-1053678473

Comment:
> As is this can't be merged due to the excessive pinning to git hashes for dependencies. Please package the dependencies as distinct packages as required per policy.

@the-maldridge This doesn't make sense for [LVGL](https://github.com/lvgl/lvgl) which is meant to be customized via header configs on a per-project basis and is built-in to the final executable (it's also included as a submodule in the git repo); so far there haven't been any packages which use LVGL in srcpkgs.

I'll see what I can do about [`squeek2lvgl`](https://gitlab.com/cherrypicker/squeek2lvgl) though, that could maybe get packaged separately.


  parent reply	other threads:[~2022-02-27 20:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-27 17:18 [PR PATCH] " JamiKettunen
2022-02-27 19:49 ` the-maldridge
2022-02-27 20:01 ` classabbyamp
2022-02-27 20:56 ` JamiKettunen
2022-02-27 20:57 ` JamiKettunen [this message]
2022-03-03  7:58 ` classabbyamp
2022-06-26  2:17 ` github-actions
2022-07-11  2:13 ` [PR PATCH] [Closed]: " github-actions
2022-11-10 19:17 ` Johennes
2022-11-10 19:24 ` classabbyamp
2022-11-10 19:32 ` Johennes

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=20220227205708.5Ibsu9EgChzGb8hOkt6YXMfQQ4m_vpMQQdIr1FZnixQ@z \
    --to=jamikettunen@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).