From: wael444 <wael444@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: grapejuice-4.8.2
Date: Wed, 12 Jan 2022 12:26:41 +0100 [thread overview]
Message-ID: <20220112112641.CQ7TqpoV0459FknJFvqSeTw1Pzukp49Fuq4Y-jkEG70@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: 829 bytes --]
New comment by wael444 on void-packages repository
https://github.com/void-linux/void-packages/pull/34998#issuecomment-1010941102
Comment:
before i update the template, i would like to ask if having `freetype-32bit, gnutls-32bit, libgcc-32bit` is appropriate to be included in the package, as it only solves problems with wine such as
libgcc-32bit:
```
libgcc_s.so.1 must be installed for pthread_cancel to work
wine client error:154: write: Bad file descriptor
```
freetype-32bit:
```
Wine cannot find the FreeType font library.
```
gnutls-32bit:
```
HttpSendRequest Failed
```
i will not be including wine as an dependency as roblox requires a different build of wine with required patches to make roblox work.
these dependencies have nothing to do with grapejuice, but only provide fixes to wine problems.
next prev parent reply other threads:[~2022-01-12 11:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 16:14 [PR PATCH] " 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 [this message]
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
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=20220112112641.CQ7TqpoV0459FknJFvqSeTw1Pzukp49Fuq4Y-jkEG70@z \
--to=wael444@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).