Package Details: waterfox-classic-kpe 2022.11-0

Git Clone URL: https://aur.archlinux.org/waterfox-classic-kpe.git (read-only, click to copy)
Package Base: waterfox-classic-kpe
Description: Customizable privacy conscious web browser with better integration with KDE
Upstream URL: https://classic.waterfox.net/
Keywords: firefox kwaterfox plasma waterfox-classic-kde waterfox-kde
Licenses: MPL
Conflicts: waterfox-classic, waterfox-kde
Provides: waterfox-classic
Replaces: waterfox-kde
Submitter: hawkeye116477
Maintainer: None
Last Packager: hawkeye116477
Votes: 9
Popularity: 0.000000
First Submitted: 2019-10-27 10:38 (UTC)
Last Updated: 2022-11-24 12:32 (UTC)

Dependencies (36)

Required by (1)

Sources (11)

Pinned Comments

hawkeye116477 commented on 2019-09-03 16:53 (UTC) (edited on 2021-03-08 11:18 (UTC) by hawkeye116477)

Binary version of this package is available on my repository on OBS and language packs are available as separete waterfox-classic-i18n-* packages.

Source files at: https://build.opensuse.org/package/show/home:hawkeye116477:waterfox/waterfox-classic-kpe. 

[home_hawkeye116477_waterfox_Arch]
Server = https://download.opensuse.org/repositories/home:/hawkeye116477:/waterfox/Arch/$arch

If you got 404, then temporarily try to replace download.opensuse.org with downloadcontent.opensuse.org. That should enforce direct download without mirror.

key=$(curl -fsSL https://download.opensuse.org/repositories/home:hawkeye116477:waterfox/Arch/$(uname -m)/home_hawkeye116477_waterfox_Arch.key)
fingerprint=$(gpg --quiet --with-colons --import-options show-only --import --fingerprint <<< "${key}" | awk -F: '$1 == "fpr" { print $10 }')

pacman-key --init
pacman-key --add - <<< "${key}"
pacman-key --lsign-key "${fingerprint}"

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

nobyte commented on 2021-10-27 09:51 (UTC)

@ranger .. ok thanks. I'll have a look at the pamac gitlab. Sorry for spamming with off topic stuff.

ranger commented on 2021-10-26 20:38 (UTC)

@nobyte

your problem is not with waterfox, is that you are using pamac The standard method (makepkg) wont delete the folder, if you want you can try. Or maybe there is an option in pamac to do that, I'm not using it

nobyte commented on 2021-10-26 19:26 (UTC)

@toxygen .. I might be having a noob problem here.

Keeping the "Waterfox" folder from previous build is what I would want. But the build process (started from pamac gui) appears to always clean up the build dir before starting to update the source dir from the repo (which leads to the whole source being downloaded again).

So in order to keep the previous source I always move the "Waterfox" dir out of the build dir before telling pamac gui to build the package (as I wrote already) and only move it back to the build dir after the cleanup .. which is after I've saved PKGBUILD changes from the gui and before I click on build.

I'm not sure if this is intended behaviour on behalf of pamac. I already asked on the Manjaro forums.

Maybe I should just build from terminal.

I just thought there ought to be an easier way, this can't be the way it's supposed to work.

Thanks anyway.

toxygen commented on 2021-10-26 16:38 (UTC)

@nobyte dont you just need to keep the "Waterfox" folder that's initially created? my process is usually download the new version aur files to a build folder, then cp over the "Waterfox" folder from the previous build in ./waterfox-classic-kpe/Waterfox, make any additional PKGBUILD changes, and makepkg from there.
the git takes a lot less than doing it from scratch for me with this process. i'm sure there's better ways tho lol

nobyte commented on 2021-10-22 10:40 (UTC)

In the beginning of the build process the source (from previous build) is always cleaned/deleted on my system (Manjaro).

This makes the monthly build take much longer, as the git index-pack step alone takes almost an hour. Also the full 5 GB of source files are always downloaded again, which is a waste of traffic. Additionally it causes lots of disk IO which is annoying on a system with HDD instead of SSD.

Is there a way to prevent the source from the previous build being deleted?

As a workaround I moved the source dir from the build dir after a completed build to somewhere else and "injected" it back to the build dir right after I saved the PKGBUILD (after customizing it for build). But this is always a hassle.

toxygen commented on 2021-04-27 14:49 (UTC)

thanks hawkeye, that fix worked

hawkeye116477 commented on 2021-04-27 11:57 (UTC)

@toxygen Oops, sorry, apparently MrAlex now didn't added classic to tag.

toxygen commented on 2021-04-27 03:23 (UTC)

here's the error, which happened again on a clean build:

fatal: invalid reference: 2021.04.2-classic ==> ERROR: Failure while creating working copy of Waterfox git repo

toxygen commented on 2021-04-27 02:36 (UTC)

I tried building 2021.04.2 and it built.. waterfox (not -classic) originally had an error about not finding tag 2021.04.2-classic, re-running makepkg re-downloaded from git, and it turned into regular waterfox

trying again now, we'll see how it goes

toxygen commented on 2020-12-02 02:16 (UTC) (edited on 2020-12-02 02:17 (UTC) by toxygen)

@hawkeye116477 I was going based on this commit https://github.com/MrAlex94/Waterfox/commit/c5807fef37c8a918c04e069173890bbeedb1ddb3

but i see what you mean, gotta wait a few more days i guess!

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »