From a552f5ab6d488f8ded3ad11cbcc49c6919a4c14e Mon Sep 17 00:00:00 2001 From: Mario Sanchez Prada Date: Wed, 20 Sep 2023 18:59:03 +0200 Subject: [PATCH] Drop links to pre-built packages from popular Linux distributions We don't control how distributions create those packages, and so we can't really recommend them from here as they might be sending the wrong message if people base their opinion on WPE based on using such packages. Until we can get our own images up and running and published on our website, we should not encourage people to use 3rd party sources. --- about/get-wpe.md | 18 ------------------ developers/index.md | 2 -- 2 files changed, 20 deletions(-) diff --git a/about/get-wpe.md b/about/get-wpe.md index 1d3e77f57..323b3fbef 100644 --- a/about/get-wpe.md +++ b/about/get-wpe.md @@ -40,7 +40,6 @@ get the source code directly and modify it to serve your needs. While this can sometimes be an involved process, there are different ways to get your hands on WPE, depending on what you need. -* [__Install it from your Linux distribution__](#install-it-from-your-linux-distribution): This is the easiest, and it allows you to quickly test WPE on the desktop. * [__Build an image for supported reference hardware__](#build-an-image-for-supported-reference-hardware): This is a bit more involved, but it's an easy way to try out WPE directly on embedded hardware. * [__Download the official tarball releases__](#download-the-official-tarball-releases): This is the best way to get periodical updates with new features and security fixes. * [__Get the source code directly from git__](#get-the-source-code-directly-from-git): This is only necessary if you want to get involved in the development of WPE. @@ -55,23 +54,6 @@ will need. The different components that are needed to run WPE are: * [WPEBackend-fdo](https://github.com/Igalia/WPEBackend-fdo): A reference FreeDesktop.org backend for WPE, that relies on different FreeDesktop.org projects and can serve as a starting point to either customize or create a completely new backend for specific configurations. * [Cog](https://github.com/Igalia/cog): A simple and minimalistic browser using WPE, with no user interface, suitable to be used as a Web application container or as a starting point to develop more complex browser applications based on WPE. -## __Install it from your Linux distribution__ - -These packages are not just a quick and simple way to test WPE but -they also come with all the development files and documentation -necessary to build and test software that uses this web engine. Some -of the distributions that already have built packages for WPE are: - - * [Debian](https://packages.debian.org/search?searchon=sourcenames&keywords=wpewebkit) - * [Ubuntu](https://packages.ubuntu.com/search?keywords=wpewebkit&searchon=sourcenames&suite=all§ion=all) - * [Raspbian](https://archive.raspbian.org/raspbian/pool/main/w/wpewebkit/) - * [Arch Linux](https://archlinux.org/packages/extra/x86_64/wpewebkit/) - * [Fedora](https://copr.fedorainfracloud.org/coprs/philn/wpewebkit/) - -This list is not exhaustive, so if you use a different distributions, -there might be packages for it already. Refer to the official -documentation of your distribution for information on how to install packages. - ## __Build an image for supported reference hardware__ A simple way to cross-compile WPE and its dependencies for a target diff --git a/developers/index.md b/developers/index.md index 5954530e2..8eb315af8 100644 --- a/developers/index.md +++ b/developers/index.md @@ -34,8 +34,6 @@ h2 { While there are several simple ways for developers to experiment with and explore WPE, none are tuned for performance. Generally, shipping products for embedded systems are performance-tuned custom builds. To make this easier, there is also [meta-webkit](https://github.com/Igalia/meta-webkit), which provides build recipes, WebKit based runtimes, and browsers for use with OpenEmbedded and/or Yocto. -There are also pre-built packages available for many Linux distributions. -