Package Details: ladybird-git r70264.8b1f1ae87ae-1

Git Clone URL: https://aur.archlinux.org/ladybird-git.git (read-only, click to copy)
Package Base: ladybird-git
Description: Truly independent web browser
Upstream URL: https://github.com/LadybirdBrowser/ladybird
Keywords: browser
Licenses: BSD-2-Clause
Conflicts: ladybird
Provides: ladybird
Submitter: xyproto
Maintainer: CxByte
Last Packager: CxByte
Votes: 23
Popularity: 2.95
First Submitted: 2022-09-12 14:59 (UTC)
Last Updated: 2025-07-10 07:44 (UTC)

Pinned Comments

CxByte commented on 2025-07-10 01:47 (UTC)

A note since this package now builds with the system libs: skia has to be installed and available through pkg-conf; skia-static provides the specific version (and a pkg-conf file) needed by this build.

Latest Comments

1 2 3 4 5 6 7 Next › Last »

CxByte commented on 2025-07-10 01:47 (UTC)

A note since this package now builds with the system libs: skia has to be installed and available through pkg-conf; skia-static provides the specific version (and a pkg-conf file) needed by this build.

Knotrocket commented on 2025-07-03 13:58 (UTC)

Upstream has bumped the vcpkg baseline to a7ef72790b3f4a6c1f940503e418f71380ac94a7 in #5264.

sixtyfive commented on 2025-06-13 16:09 (UTC)

@dlazar, happy to help! When you use yay and there's been an update to the Ladybird sources, it'll clone and build the whole thing all over again. Foregoing the convenience of yay and using makepkg directly will keep the same source tree clone intact. Therefore, your old CPUs will only have to compile the parts of it that have changed.

dlazar commented on 2025-06-13 16:01 (UTC)

@sixtyfive

That is all I meant by macro! The short list of commands to run to use ladybird, but also keep it up to date. Of course, seeing the makepkg command means this will be a laborious task for the old CPUs, but that is fine! Thanks for the info.

sixtyfive commented on 2025-06-13 15:57 (UTC)

@dlazar Dave, I don't know what you mean by "macro". For something like Ladybird, at its current stage of development, I would just not use yay at all. I'd clone this AUR repository and run makepkg myself whenever I wanted to update:

git clone https://aur.archlinux.org/ladybird-git.git
cd ladybird-git
makepkg -i

You'll have the Ladybird git repository available directly that way. No cache directory hidden away somewhere.

dlazar commented on 2025-06-13 14:36 (UTC)

@sixtyfive, what would you recommend as a "try this macro" way of going about experimenting with ladybird browser then, at this stage of its existence? While you point to an alternative to yay -S ladybird-git I am not sure I follow what a superior method might be? Could you kindly paste one here for me to learn from?

sixtyfive commented on 2025-06-13 14:29 (UTC)

@dlazar you might want to not use AUR helpers like yay for big source packages like this.

dlazar commented on 2025-06-13 14:08 (UTC)

I am at a bit of a loss here, but as this project develops, is it standard that now that I have successfully compiled the AUR version of this, resulting in a working binary on my machine, that I now do a git pull, when desired, and re-compile from scratch, thus smoking my machine for as long as it takes? I believe at some point it'll be a routine binary to download, but for now, it's all or nothing in recompiling from scratch, right?

dreieck commented on 2025-06-13 12:04 (UTC)

vcpkg is now in the repositories.

Can you maybe just use that package, instead of cloning it's sources (again)?

Regards!

dlazar commented on 2025-06-12 14:09 (UTC)

I started a build fresh and from scratch and this time it completed without errors, so it appears pulling fresh code from git worked to smooth over the inconsistencies. Browser is working. Thanks!

1 2 3 4 5 6 7 Next › Last »