Package Details: qtwebkit 2.3.4-9

Git Clone URL: https://aur.archlinux.org/qtwebkit.git (read-only, click to copy)
Package Base: qtwebkit
Description: An open source web browser engine (Qt port)
Upstream URL: http://trac.webkit.org/wiki/QtWebKit
Licenses: GPL3, LGPL2.1
Conflicts: qt
Submitter: arojas
Maintainer: Omar007
Last Packager: Omar007
Votes: 54
Popularity: 0.046258
First Submitted: 2017-02-09 07:52 (UTC)
Last Updated: 2023-04-30 16:17 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 16 Next › Last »

Ulin commented on 2017-07-04 00:07 (UTC)

http://archlinux.kuzbass.net/other/packages/qtwebkit/qtwebkit-2.3.4.tar.xz !!!!!! DELETE: https://sources.archlinux.org/other/packages/qtwebkit/qtwebkit-2.3.4.tar.xz

yaron commented on 2017-06-30 06:46 (UTC)

I just tried installing on latest Manjaro and got this: ===== BUILD FAILED ====== The build failed with exit code 2. This may have been because you - added an #include to a source/header - added a Q_OBJECT macro to a class - added a new resource to a qrc file as dependencies are not automatically re-computed for local developer builds. You may try computing dependencies manually by running 'make qmake' in: /tmp/yaourt-tmp-yaron/aur-qtwebkit/src/qtwebkit-2.3.4/WebKitBuild/Release or passing --makeargs="qmake" to build-webkit. =========================

WoefulDerelict commented on 2017-06-28 03:02 (UTC) (edited on 2017-06-28 14:18 (UTC) by WoefulDerelict)

8BitSloth: Sadly there really isn't much one can do to the PKGBUILD to remedy the build issues encountered by some users. In my tests it was interactions with libxslt that lead to the build failing. While it takes some time users can successfully build this in a clean chroot. The devtools package provides scripts to automate this process. aurutils is also capable of aiding with builds of things from the AUR in a clean chroot.

8BitSloth commented on 2017-06-27 20:37 (UTC)

This package is still unusable. WoefulDerelict, you should really request this package be orphaned then take control of it. You've done more in the last 6 months than the maintainer.

WoefulDerelict commented on 2017-06-12 18:50 (UTC) (edited on 2017-06-12 19:44 (UTC) by WoefulDerelict)

bigdaddy: You're problem is Manjaro. Like many Manjaro packages their devtools deployment is not the same as the package distributed for Arch Linux proper. You can inspect the Arch Linux package and list the included files via the web interface and see that the distributed files do not match the devtools package for Manjaro: [https://www.archlinux.org/packages/extra/any/devtools/] I suspect the proper script when using Manjaro is 'stable-x86_64-build' given the options available; however, it may be prudent to visit the equivalent wiki entry for Manjaro's devtools package to familiarise yourself with their quirks.

tillyboy commented on 2017-06-12 14:54 (UTC)

Thank you really much! Unfortunately, even though I have installed devtools, the script is not available. An excerpt from pacman -Qt devtools gives me the following: devtools /usr/bin/arch-nspawn devtools /usr/bin/archbuild devtools /usr/bin/checkpkg devtools /usr/bin/find-libdeps devtools /usr/bin/find-libprovides devtools /usr/bin/finddeps devtools /usr/bin/lddd devtools /usr/bin/makechrootpkg devtools /usr/bin/manjaro-nspawn devtools /usr/bin/manjarobuild devtools /usr/bin/mkarchroot devtools /usr/bin/mkmanjaroroot devtools /usr/bin/signpkg devtools /usr/bin/signpkgs devtools /usr/bin/stable-i686-build devtools /usr/bin/stable-multilib-build devtools /usr/bin/stable-x86_64-build devtools /usr/bin/testing-i686-build devtools /usr/bin/testing-multilib-build devtools /usr/bin/testing-x86_64-build devtools /usr/bin/unstable-i686-build devtools /usr/bin/unstable-multilib-build devtools /usr/bin/unstable-x86_64-build devtools /usr/share/ devtools /usr/share/bash-completion/ devtools /usr/share/bash-completion/completions/ devtools /usr/share/bash-completion/completions/devtools devtools /usr/share/devtools/ devtools /usr/share/devtools/makepkg-i686.conf devtools /usr/share/devtools/makepkg-x86_64.conf devtools /usr/share/devtools/pacman-default.conf devtools /usr/share/devtools/pacman-mirrors-stable.conf devtools /usr/share/devtools/pacman-mirrors-testing.conf devtools /usr/share/devtools/pacman-mirrors-unstable.conf devtools /usr/share/devtools/pacman-multilib.conf devtools /usr/share/zsh/ devtools /usr/share/zsh/site-functions/ devtools /usr/share/zsh/site-functions/_devtools Maybe it is worth noting that I do not run Arch but Manjaro, but usually any fixes related to Arch worked for me as well.

WoefulDerelict commented on 2017-06-12 06:09 (UTC) (edited on 2017-06-28 14:22 (UTC) by WoefulDerelict)

There are a handful of useful scripts packaged together that simplify building packages in a clean chroot. These are maintained by the distribution as a convenience for developers and end users alike. These tools are documented in the DeveloperWiki here: [https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot] A summary of the necessary steps to manually build this package in a clean chroot using 'extra-x86_64-build' from the devtools package follows. Prerequisites: Install the devtools package from [Extra] as the script used is provided by this package. 1. Clone the qtwebkit repository or extract the snapshot archive into a clean working directory. 2. Enter the directory containing the package source. (PKGBUILD and patches.) 3. Execute the following command: extra-x86_64-build 4. Call pacman with the -U flag to install the resulting package. [https://wiki.archlinux.org/index.php/pacman#Additional_commands]

severach commented on 2017-06-11 17:20 (UTC)

The hard way is to follow the clean chroot instructions on the wiki. The easy way is to install Graysky's clean-chroot-manager and let it do all the heavy lifting.

tillyboy commented on 2017-06-11 12:21 (UTC) (edited on 2017-06-11 12:22 (UTC) by tillyboy)

Is there any fix currently so that the package can be built (semi-)manually? I am new to linux and therefore unable to decipher the suggestions given below (i.e. building in a clean chroot etc.). Sorry for that but I would really appreciate if there was somebody explaining how to get this thing to build. Thanks in advance for that. Also why does yaourt tell that this is out of date?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 16 Next › Last »