Github messages for voidlinux
 help / color / mirror / Atom feed
From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: packages broken by cmake build-style change
Date: Mon, 25 Dec 2023 04:03:18 +0100	[thread overview]
Message-ID: <20231225030318.cisRMTtx0AgPit1ie0fJhqMI3KTZdjl4VwR4jAZK1rY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45679@inbox.vuxu.org>

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

New comment by 0x5c on void-packages repository

https://github.com/void-linux/void-packages/issues/45679#issuecomment-1868688606

Comment:
> https://github.com/void-linux/void-packages/commit/3468a5f0bc3c19b3abe54c8d17310eb90679cc79

Thanks!

> Is there a way I can create a working template for ueberzugpp, or do I need to wait until GSL and CLI11 are packaged?

For CLI11, I recommend trying to package it yourself, it doesn't look complex and is header-only; it might not need anything more than the cmake build style, a couple of `configure_args`, and a vlicense. If you do that, have it be added in a separate commit in the same PR as ueberzugpp. You can ping me in the PR you make if you need help, and don't hesitate to open a PR as draft.

For GSL, I recommend waiting for the PR to get merged (there will be problems if two PR get merged that add the same package). Although, if you're comfortable enough with git and make sure to use a draft PR, you could temporarily pull my GSL commit from the contour PR. Your PR would still have to wait for GSL to merge, but you'd be able to build and test the package.

  parent reply	other threads:[~2023-12-25  3:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-20  0:25 [ISSUE] " classabbyamp
2023-08-20  0:30 ` sgn
2023-08-20  2:51 ` classabbyamp
2023-08-22 21:24 ` motorto
2023-08-29 14:10 ` sgn
2023-12-24 19:35 ` d4r1us-drk
2023-12-24 21:17 ` 0x5c
2023-12-24 22:08 ` d4r1us-drk
2023-12-24 22:11 ` d4r1us-drk
2023-12-24 22:53 ` 0x5c
2023-12-25  1:00 ` d4r1us-drk
2023-12-25  1:07 ` classabbyamp
2023-12-25  1:56 ` sgn
2023-12-25  2:10 ` 0x5c
2023-12-25  2:13 ` d4r1us-drk
2023-12-25  2:15 ` sgn
2023-12-25  2:16 ` sgn
2023-12-25  2:17 ` sgn
2023-12-25  2:17 ` sgn
2023-12-25  2:19 ` d4r1us-drk
2023-12-25  3:03 ` 0x5c [this message]
2023-12-25  3:07 ` d4r1us-drk
2024-04-18  7:33 ` [ISSUE] [CLOSED] " classabbyamp
2024-04-18  7:33 ` classabbyamp
2024-04-19  4:43 ` ibhagwan
2024-04-20 20:24 ` d4r1us-drk
2024-04-20 20:25 ` d4r1us-drk

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=20231225030318.cisRMTtx0AgPit1ie0fJhqMI3KTZdjl4VwR4jAZK1rY@z \
    --to=0x5c@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).