From: Oreo639 <Oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Adding x86_64 package to wine
Date: Mon, 17 Feb 2020 20:02:49 +0100 [thread overview]
Message-ID: <20200217190249.ngJ9SlEw22AQVfNakXwkr-aGNmdRq48rIE6zYr-PMAY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17678@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
New comment by Oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/17678#issuecomment-587122598
Comment:
The log too long issue in travis can be worked around by using [ci skip] in the commit message to skip travis building. It isn't the reason this pr likely won't get merged though.
As for why wine x86_64 likely won't get merged as was said before. xbps-src is supposed to let you build a package without any precompiled dependencies (it automatically builds them beforehand if they aren't in the repos). However it can't automatically cross compile 32-bit dependencies. If it tries to build a -32bit dependency in 64bit mode it will just make a 64bit package. You have to cross compile all the 32-bit dependencies beforehand. Thus it requires precompiled 32bit dependencies in the repos in order to work which is not optimal.
From Hoshpak:
>However void-packages is built on the premise that it is possible to bootstrap everything from sources without requiring any preexisting binary packages. So I should be able to always just clone this repository, not use any of the mirrors and build a whole system from the sources.
Also your commit log doesn't follow the commit style guide.
If I am mistaken please correct me.
next prev parent reply other threads:[~2020-02-17 19:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17678@inbox.vuxu.org>
2020-01-08 3:21 ` voidlinux-github
2020-01-22 14:09 ` voidlinux-github
2020-01-23 7:47 ` voidlinux-github
2020-01-23 8:31 ` voidlinux-github
2020-01-23 8:38 ` voidlinux-github
2020-01-23 17:56 ` voidlinux-github
2020-01-23 18:01 ` voidlinux-github
2020-01-23 18:04 ` voidlinux-github
2020-01-23 18:07 ` voidlinux-github
2020-01-23 19:53 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-24 0:48 ` voidlinux-github
2020-02-17 19:01 ` Oreo639
2020-02-17 19:02 ` Oreo639 [this message]
2020-02-17 19:05 ` Oreo639
2020-02-17 20:39 ` Oreo639
2020-02-20 0:00 ` bugcrazy
2020-02-20 0:04 ` Duncaen
2020-02-20 0:04 ` Duncaen
2020-04-09 21:58 ` [PR PATCH] [Updated] " bugcrazy
2020-04-10 0:13 ` bugcrazy
2020-04-10 1:40 ` bugcrazy
2020-04-15 22:24 ` bugcrazy
2020-05-03 14:46 ` Hoshpak
2020-05-03 14:46 ` [PR PATCH] [Closed]: " Hoshpak
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=20200217190249.ngJ9SlEw22AQVfNakXwkr-aGNmdRq48rIE6zYr-PMAY@z \
--to=oreo639@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).