Github messages for voidlinux
 help / color / mirror / Atom feed
From: Sqvid <Sqvid@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: raylib-4.0.0
Date: Fri, 23 Dec 2022 18:13:53 +0100	[thread overview]
Message-ID: <20221223171353.HHH73HV8Gin-idw7YCoT8ntfYLKlVsQjLZT5xMYcKFA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41218@inbox.vuxu.org>

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

New comment by Sqvid on void-packages repository

https://github.com/void-linux/void-packages/pull/41218#issuecomment-1364124763

Comment:
> It's very simple to setup raylib as a dependency with meson's wrapdb. This package doesn't make much sense for building some games that need raylib because we would soon have to have multiple raylib versions at the same time. It also doesn't make sense for development because there you want to develop with one version and not worry about it changing under your hands.

Thank you for taking the time to review my PR, and for the feedback. You are absolutely right about the API changes. I do agee that games built on raylib are best off statically linking. But for new developers, experimenting with the library, don't the releases make sense? As far as I can see new releases come out ~6months and upstream encourages users to use their distros version if possible. And indeed [several other distros do package it](https://repology.org/project/raylib/versions). Perhaps there is some utility to new developers who want to rely on versioned releases?

> I do not think this is a good fit for a void package.
However, I am very happy to admit my inexperience in this area, so please feel free to close the PR if this is not sensible and there is no way to make it work. Thank you for your time.


  parent reply	other threads:[~2022-12-23 17:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 18:39 [PR PATCH] " Sqvid
2022-12-21 18:46 ` Sqvid
2022-12-21 18:47 ` Sqvid
2022-12-21 18:48 ` [PR PATCH] [Updated] " Sqvid
2022-12-23 13:17 ` Sqvid
2022-12-23 13:23 ` Sqvid
2022-12-23 17:13 ` Sqvid
2022-12-23 17:13 ` Sqvid [this message]
2022-12-23 17:14 ` Sqvid
2023-02-08 17:14 ` [PR PATCH] [Closed]: " Sqvid

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=20221223171353.HHH73HV8Gin-idw7YCoT8ntfYLKlVsQjLZT5xMYcKFA@z \
    --to=sqvid@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).