Package Details: palemoon 1:33.4.0.1-1

Git Clone URL: https://aur.archlinux.org/palemoon.git (read-only, click to copy)
Package Base: palemoon
Description: Open source web browser based on Firefox focusing on efficiency.
Upstream URL: https://www.palemoon.org/
Keywords: browser goanna web
Licenses: MPL-2.0
Submitter: artiom
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 142
Popularity: 0.27
First Submitted: 2014-06-05 10:54 (UTC)
Last Updated: 2024-10-09 21:58 (UTC)

Pinned Comments

WorMzy commented on 2021-03-02 16:19 (UTC) (edited on 2022-08-03 21:12 (UTC) by WorMzy)

The following key is used to sign release commits:

40481E7B8FCF9CEC

Import it into your keyring however you want.

https://wiki.archlinux.org/index.php/GnuPG#Import_a_public_key

Latest Comments

« First ‹ Previous 1 .. 24 25 26 27 28 29 30 31 32 33 34 .. 38 Next › Last »

prettyvanilla commented on 2016-08-07 21:31 (UTC)

It's not quite the same point in this case, as extra/firefox also still compiles against system libraries. (Besides, I don't believe the Arch Linux ideals of simplicity include *not* unbundling libraries if upstream's build system explicitly provides for building against system libs.) Anyway, it's not really a problem for me to just leave the respective options in on my local system if you decide to go with Matt's/Pale Moon's request.

WorMzy commented on 2016-08-07 15:51 (UTC)

It's the same point as using Arch's extra/firefox instead of downloading mozilla's precompiled firefox binaries from getfirefox.com. Of course, if you don't want to compile your own due to the perceived lack of benefit, you can always use palemoon-bin.

Arvedui commented on 2016-08-07 10:44 (UTC)

Where is the point in this package if it just replicates the binary distribution from upstream?

WorMzy commented on 2016-08-06 21:30 (UTC)

Hi Matt, that's not a problem. One of the main Arch Linux ideals is shipping software as close to what upstream recommends, so the more explicit recommendations on the dev wiki, the better! I was going to remove the system lib lines from my mozconfig for the next point release of PM, but I'll push it out shortly instead since you recommend against using them.

mattatobin commented on 2016-08-06 16:36 (UTC)

@wolf At this point we can say the current codebase SHOULD be good with GCC5 but GCC6 is simply not supported and won't be. Work on GCC6 support has shifted to the new milestone that will become Pale Moon 27. @WorMzy After some consideration, also not related to this GCC but general building.. We, Pale Moon, would prefer if you would go ahead and stop building with system libs period (beyond --with-phthreads). I want to start an initiative to standardize and sync package maintainers and our generic linux configuration. The intention is to keep packages maintained by .. package maintainers as close to our official generic linux package as possible to avoid any potential issues from different configuration and compiling quirks. Configuration and Compiling differences SHOULD be limited in scope to those absolutely required for a successful and operational build for the target platform and system but otherwise follow our official setup as closely as possible. Please see the (now being revised) Developer Wiki page for Building Pale Moon for Linux here: http://developer.palemoon.org/Developer_Guide:Build_Instructions/Pale_Moon/Linux Mainly, the .mozconfig shouldn't need to diverge from our official one much if at all.

wolf commented on 2016-07-31 20:51 (UTC)

Nope, couldn't make it work with gcc6, so I returned to gcc5 for the moment. Ok, got a workaround, apparently it doesn't like something in my .bashrc. Sry for wasting your time, issue was on my end :)

WorMzy commented on 2016-07-31 20:26 (UTC)

I can't reproduce that here. Are you still building with gcc6? Any other mozconfig/PKGBUILD changes? Have you made any changes to your /etc/makepkg.conf? If there's nothing obvious causing this on your end, try building in a clean chroot [1] (I actually recommend doing this anyway, for all AUR/ABS packages). [1] https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot

wolf commented on 2016-07-31 18:23 (UTC)

Cannot build, getting following error: ==> Making package: palemoon 26.3.3-3 (Sun Jul 31 19:49:06 CEST 2016) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Updating Pale-Moon git repo... Fetching origin -> Found mozconfig.in ==> Validating source files with md5sums... Pale-Moon ... Skipped mozconfig.in ... Passed ==> Extracting sources... -> Creating working copy of Pale-Moon git repo... Cloning into 'Pale-Moon'... done. Checking out files: 100% (80809/80809), done. Switched to a new branch 'makepkg' ==> Starting prepare()... ==> Starting build()... Creating global state directory from environment variable: /home/wolfie/archrepo/palemoon/src/mozbuild Please re-run mach. Next => 0:00.40 /usr/bin/make -f client.mk -s 0:00.59 client.mk:118: *** missing separator. Stop. 0:00.63 0 compiler warnings present. ==> ERROR: A failure occurred in build(). Aborting...

0strodamus commented on 2016-07-29 18:07 (UTC)

Thanks for the palemoon info and for teaching me something I did not know about pacman's local database!

WorMzy commented on 2016-07-29 10:54 (UTC)

You're right about the deps, I've removed both nss and nspr from the array. I've not bumped the pkgrel though, as the compiled package is still the same and most people probably aren't too bothered by the extra 7MB of deps. Rebuild the package if you want to strip out those deps, or if you know what you're doing, modify pacman's database manually (/var/lib/pacman/local/palemoon-26.3.3-3/desc). The config options in question look to be disabled by default, but explicitly disabling them shouldn't cause any problems.

« First ‹ Previous 1 .. 24 25 26 27 28 29 30 31 32 33 34 .. 38 Next › Last »