Github messages for voidlinux
 help / color / mirror / Atom feed
From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: KDE Gear update to: 22.12.3
Date: Wed, 22 Mar 2023 08:32:51 +0100	[thread overview]
Message-ID: <20230322073251.ZD_8IzWp8q3S3ob85MeFP1kdTTrPP2sa-MtR5CvsLU0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42875@inbox.vuxu.org>

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

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/pull/42875#issuecomment-1479038748

Comment:
> So far it's been running smoothly, I've been using it for 3 days

Good! Not everyone is going to take their time to test that lot.

> what if a package requires dependencies from another PR

Prefer to split in a way where dependencies are in same PR. In this case, you can split off games, kdevelop and packages failing tests and the rest should fit. In general case libraries rebuild may cause need to rebuild all dependants, but here apps would just build with previous version.

  parent reply	other threads:[~2023-03-22  7:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20  3:30 [PR PATCH] " hervyqa
2023-03-20  4:13 ` hervyqa
2023-03-20  6:22 ` Chocimier
2023-03-20  7:46 ` hervyqa
2023-03-20  7:47 ` hervyqa
2023-03-20  7:53 ` hervyqa
2023-03-20 23:26 ` Chocimier
2023-03-22  1:07 ` hervyqa
2023-03-22  7:32 ` Chocimier [this message]
2023-03-22 23:32 ` hervyqa
2023-03-22 23:33 ` hervyqa
2023-04-25 16:40 ` Chocimier
2023-04-25 16:40 ` [PR PATCH] [Closed]: " Chocimier
2023-04-26  0:29 ` hervyqa

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=20230322073251.ZD_8IzWp8q3S3ob85MeFP1kdTTrPP2sa-MtR5CvsLU0@z \
    --to=chocimier@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).