Github messages for voidlinux
 help / color / mirror / Atom feed
From: karimrir1 <karimrir1@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: grapejuice-4.9.2
Date: Thu, 13 Jan 2022 10:19:20 +0100	[thread overview]
Message-ID: <20220113091920.ktPlVRZNemq8771fmYOe36WdlQG8qq3JIA7UcrRz1CE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34998@inbox.vuxu.org>

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

New comment by karimrir1 on void-packages repository

https://github.com/void-linux/void-packages/pull/34998#issuecomment-1011928872

Comment:
> To sum up:
> 
>     * this is launcher of single proprietary game
> 
>     * moving fast
> 
>     * that can't be installed with dependencies of game due to way void multilib works
> 
>     * requiring wine built from source separately (up to 1 hour build time)
> 
>     * being pure python module buildable within minutes
> 
> 
> Sorry, but it is not worthwhile to package this. However, after restoring -32bit dependencies jut for glibc x86_64, you have nice template you can share somewhere else.

It's not a launcher, It's a wrapper for wine. Just like lutris. Nothing else nothing more.

Edit: If you were right about being it a launcher for a proprietary game, then why is there a MultiMC package?? Isn't MultiMC a launcher for a single proprietary game?

I never intended to insult you, I was just trying to make you understand that Grapejuice is a wrapper, not a launcher. I honestly appreciate the work you guys do at the void linux project. I even installed void linux on my mom's laptop (because void linux is pretty low in terms of memory usage and her computer is yet just another bootloader to Google Chrome.)

      parent reply	other threads:[~2022-01-13  9:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 16:14 [PR PATCH] New package: grapejuice-4.8.2 wael444
2022-01-11 17:05 ` [PR PATCH] [Updated] " wael444
2022-01-11 17:34 ` Chocimier
2022-01-11 17:37 ` cinerea0
2022-01-11 18:42 ` wael444
2022-01-11 18:43 ` cinerea0
2022-01-11 18:49 ` wael444
2022-01-11 18:57 ` z-ffqq
2022-01-11 18:59 ` z-ffqq
2022-01-11 19:00 ` z-ffqq
2022-01-11 19:01 ` z-ffqq
2022-01-11 19:07 ` z-ffqq
2022-01-12  9:15 ` z-ffqq
2022-01-12 11:26 ` wael444
2022-01-12 14:26 ` wael444
2022-01-12 19:01 ` [PR PATCH] [Updated] " wael444
2022-01-12 19:21 ` [PR PATCH] [Closed]: New package: grapejuice-4.9.2 Chocimier
2022-01-13  8:58 ` karimrir1
2022-01-13  9:11 ` karimrir1
2022-01-13  9:19 ` karimrir1 [this message]

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=20220113091920.ktPlVRZNemq8771fmYOe36WdlQG8qq3JIA7UcrRz1CE@z \
    --to=karimrir1@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).