Github messages for voidlinux
 help / color / mirror / Atom feed
From: blacklightpy <blacklightpy@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: newm-0.2
Date: Tue, 26 Mar 2024 23:44:00 +0100	[thread overview]
Message-ID: <20240326224400.62B7C21BEC@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49555@inbox.vuxu.org>

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

New comment by blacklightpy on void-packages repository

https://github.com/void-linux/void-packages/pull/49555#issuecomment-2021593225

Comment:
> I wanted to ask you an advice: what if I have multiple distfiles and i need both of them to go through packaging script - both of them to build separately. Could it be managed within one template?
> 
> I'm asking as hewm has separate release for it's engine. I don't want to separate as void packages them because: 1) it'd be too much attention for such thing 2) LICENSE file is able within only one of them

I found this: https://github.com/void-linux/void-packages/pull/41185#discussion_r1055638769


  parent reply	other threads:[~2024-03-26 22:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26 19:14 [PR PATCH] New package: python3-dasbus-1.7 iFoundSilentHouse
2024-03-26 19:18 ` ahesford
2024-03-26 19:20 ` [PR PATCH] [Updated] " iFoundSilentHouse
2024-03-26 19:49 ` iFoundSilentHouse
2024-03-26 19:58 ` iFoundSilentHouse
2024-03-26 20:53 ` New package: newm-0.2 iFoundSilentHouse
2024-03-26 22:44 ` blacklightpy [this message]
2024-03-26 23:02 ` iFoundSilentHouse
2024-03-26 23:35 ` ahesford

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=20240326224400.62B7C21BEC@inbox.vuxu.org \
    --to=blacklightpy@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).