Package Base Details: darling-git

Git Clone URL: https://aur.archlinux.org/darling-git.git (read-only, click to copy)
Keywords: Darwin Emulator macOS OSX Wine
Submitter: UnicornDarkness
Maintainer: ralphptorres
Last Packager: facekapow
Votes: 41
Popularity: 0.007558
First Submitted: 2013-06-29 15:19 (UTC)
Last Updated: 2023-10-15 18:57 (UTC)

Pinned Comments

jamesbrink commented on 2019-07-10 02:27 (UTC)

Please use this package for stable more reliable builds

https://aur.archlinux.org/packages/darling/

This one is identical but locked in on a last known working git ref and I will update as often as I can.

I have also raised an issue about versioning so maybe we can get some kind of tags for future versions and stable working builds

https://github.com/darlinghq/darling/issues/537

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 17 Next › Last »

UnicornDarkness commented on 2016-03-02 08:42 (UTC)

Fixed, thank you! I need to find an other way with submodules...

wenLiangcan commented on 2016-03-02 02:10 (UTC)

Integrity checks (md5) differ in size from the source array.

wenLiangcan commented on 2016-02-29 00:55 (UTC)

Great!

UnicornDarkness commented on 2016-02-28 19:25 (UTC)

@wenLiangcan: why not. I do that now (1192.c931b5b-1). :)

wenLiangcan commented on 2016-02-28 12:30 (UTC) (edited on 2016-02-28 12:31 (UTC) by wenLiangcan)

I think the release number should be reset to 1 after updating the version code rather than increasing it.

UnicornDarkness commented on 2016-02-28 10:57 (UTC)

@wenLiangcan: it's added in darling-git-1188.1ab9cc2-18.

wenLiangcan commented on 2016-02-28 03:21 (UTC)

Compiled successfully, thanks for the notification @Xorg. And there's some repos should be addedd to the source list: 'git+https://github.com/darlinghq/darling-gnutar.git' 'git+https://github.com/darlinghq/darling-gpatch.git' 'git+https://github.com/darlinghq/darling-gnudiff.git'

UnicornDarkness commented on 2016-02-27 20:05 (UTC)

@wenLiangcan: it's fixed in 1183.abf5770f. ;)

UnicornDarkness commented on 2016-02-27 12:01 (UTC)

I don't know which package update cause this issue. :/ It seems it's related to 32-bit build only.

wenLiangcan commented on 2016-02-27 11:58 (UTC)

So, we have to wait for the upstream patch again :)