Package Details: firedragon 1:11.21.0_1-1

Git Clone URL: https://aur.archlinux.org/firedragon.git (read-only, click to copy)
Package Base: firedragon
Description: Floorp fork build using custom branding and settings
Upstream URL: https://firedragon.garudalinux.org
Keywords: browser firedragon firefox floorp
Licenses: MPL2
Replaces: firedragon-next
Submitter: polyzen
Maintainer: dr460nf1r3 (FGD, garudalinux)
Last Packager: garudalinux
Votes: 23
Popularity: 0.32
First Submitted: 2021-04-22 10:57 (UTC)
Last Updated: 2024-11-24 16:56 (UTC)

Dependencies (52)

Sources (3)

Pinned Comments

dr460nf1r3 commented on 2024-04-17 16:23 (UTC) (edited on 2024-04-17 16:26 (UTC) by dr460nf1r3)

Everyone can now participate in the general package update process! The process is almost entirely automated, these are the necessary steps:

  1. Create an MR with your changes to the source repo (the firedragon folder contains the files of this repo)
  2. Wait for a maintainer to review and merge it
  3. Done! When merging, the PKGBUILD will automatically be deployed to AUR via the CI pipeline.

FGD commented on 2024-02-03 22:31 (UTC)

We are finally there! After being frozen on version 119 and investing quite some time improving the app, Firedragon now has an entirely new base!

Please see the Announcement post:

https://forum.garudalinux.org/t/new-firedragon-major-version-is-out/34585

Latest Comments

1 2 3 4 5 6 .. 12 Next › Last »

dreieck commented on 2024-08-24 21:01 (UTC)

Ahoj,

optional dependency pulseaudio should be replaced by pulse-native-provider.

Regards!

Ralf_Mardorf commented on 2024-08-24 04:12 (UTC)

Thank you :)

Ralf_Mardorf commented on 2024-08-23 15:09 (UTC) (edited on 2024-08-23 15:13 (UTC) by Ralf_Mardorf)

Hi,

please, don't misuse the package release for the unusual versioning of upstream.

If upstream's versioning is 1.2.3-1 then make the pkgver 1.2.3.1, if it's 1.2.3-1.1 then make the pkgver 1.2.3.1.1. For example take a look at how it is done for extra/linux-rt or extra/linux-rt-lts.

Leave the pkgrel to the package release -1, -2, -3 and leave dotted pkgrel to the users, so a user can build an individual -1.1, -1.2 etc. and automatically follow the AUR, if the package maintainer bumps the pkgver or pkgrel.

Don't break the pkgrel, just because upstream does use such an odd versioning. The pkgrel is for the package release, not for the upstream version.

Regards, Ralf

Correction: Replace the "-" by a "_", see https://wiki.archlinux.org/title/PKGBUILD#pkgver

dr460nf1r3 commented on 2024-04-17 16:23 (UTC) (edited on 2024-04-17 16:26 (UTC) by dr460nf1r3)

Everyone can now participate in the general package update process! The process is almost entirely automated, these are the necessary steps:

  1. Create an MR with your changes to the source repo (the firedragon folder contains the files of this repo)
  2. Wait for a maintainer to review and merge it
  3. Done! When merging, the PKGBUILD will automatically be deployed to AUR via the CI pipeline.

dr460nf1r3 commented on 2024-03-20 08:29 (UTC)

I already noticed as well. Will push the change to AUR soon. Regarding the closed source Floorp components, I have been in contact with Ryosuke and now have access to the closed source. I propose creating an issue at GitLab to discuss how to move forward regarding this topic.

stefanwimmer128 commented on 2024-03-20 08:11 (UTC)

Hey @dr46onf1r3, it looks like the problem is with translations, the l10n-central submodule should be at commit b1cfac382d73f99251cf3e7076cc90e4612572f6 instead of 4c2c1ca3e907d8ce170be6770d892d17e08c0e56.

dr460nf1r3 commented on 2024-03-20 07:28 (UTC)

Interesting @xiota. In the build using the newest sources the "design" pane no longer opens successfully - has it been among the removed features? I can't find any issue or information about this change.. other than the floorp-core repo now having a private parts submodule.

xiota commented on 2024-03-19 22:23 (UTC)

Floorp removed several features a few days before releasing 11.11.0 in floorp/789a23c. Those who don't use those features may consider it a revival of the lightning build.

xiota commented on 2024-02-21 01:54 (UTC) (edited on 2024-02-21 02:12 (UTC) by xiota)

Multiple users have reported problems with DRI/zink across different Firefox forks, so may be worth including export LIBGL_ALWAYS_SOFTWARE=true with the other exports in build().

As far as I can tell, --enable-bundled-fonts is enabled by default and only bundles TwemojiMozilla.ttf. All Firefox forks I've examined include this font. To see examples, run pacman -Fl | grep TwemojiMozilla.ttf | sed -E 's& .*$&&'

To "normalize" the font list, create a new key font.system.whitelist with a list of desired fonts. The list used by torbrowser is at tor-browser/001-base-profile.js. (Some of the Noto fonts in the list are missing or have different names on Arch.)

1 2 3 4 5 6 .. 12 Next › Last »