Matching the openRC ones. Also make use of the hexagonrpcd_fw_dir env var
and reuse the correcponding conf files, making it easier to support
both init systems.
Drop all uses of the /etc/skel feature for adding configuration files and
scripts to the user's $HOME. Files installed via /etc/skel are outside the
control of the package manager and may result in broken installations. At the
least, they are not updateable from the packaging.
To implement this:
* drop $HOME/.protip_shell.sh, whose usefulness is questionable
* relocate i3blocks blocklets to /usr/share, and the config file to /etc/xdg,
which is an i3blocks' standard search path (`man i3blocks`)
* move the i3 configuration file to /etc/xdg, from where it can be picked up
and included by the config file provided via postmarketos-ui-i3wm. Configs
from $HOME are still parsed, and will be honored by i3wm, subject to i3's
limitations in connection with including extra config files
* at i3 startup, with the help of an external script, ensure there is an i3
config file in $HOME, even if empty. This prevents i3-config-wizard from
running and mangling the config files
* convert xdefaults to Xresources and store in /usr/share/X11. Load it to on
the environment by calling `xrdb` during i3 startup
Gstreamer enables hw de- and encoding by default for the most common APIs,
including V4L2-stateful. Unfortunately the venus driver is still quite
unstable, reliably crashing in very common scenarios, triggering apps
like Snapshot, Showtime or Tuba to show error messages or not working
properly - partly because of non-optimal error-handling.
Until the kernel driver situation improves, set environment variables
that demote the decoders to fallbacks in case nothing else is available,
and disable the hw-encoders completely as they tend to destabalise the
whole system if something goes wrong.
Useful command for env variables:
systemctl --user show-environment
This MR adds the boilerplate packaging needed for Mediaberry.
mbrt and sysapps are not included in this MR because Alpine Linux does not (yet?) package CEF.
For transparency: The packages here are based on the code from https://codeberg.org/lasagna/lasagna-pmaports.
[ci:skip-build]: CI fails cause of fakeroot on armv7 - known issue with CI.
Pretty sure when you already have a-z specified as range, second one
should be A-Z and not A-z.
Signed-off-by: Alexey Minnekhanov <alexeymin@postmarketos.org>
Since 1.15.11 this is supported (see
https://github.com/flatpak/flatpak/pull/5688/files). According
to the docs:
System-wide remotes can be statically preconfigured by dropping
flatpakrepo files into /usr/share/flatpak/remotes.d/ and
/etc/flatpak/remotes.d/. If a file with
the same name exists in both, the file under
/etc will take precedence.
This allows us to move the file without fear that if users disabled
or modified the repo, apk will keep the file in /etc and we won't
override it.
This is part of a wider effort to move things out of /etc and
into /usr
Fixes#2596
[ci:skip-build]: already built successfully in CI
It is needed by udev, which is in initfs-extra. If libkmod and its
dependencies are put in the first initfs then the boot.img size
increases by roughly 2 MB, which is a problem for devices with small
boot partitions.
Fixes: postmarketOS/pmaports#3510
[ci:skip-build]: already built successfully in CI (riscv64 failed
because of know qemu CI issue)
Add a note with the reason for archiving and a suggestion to use the generic port (qcom-msm8953), remove maintainers. These individual ports was replaced (MR 5800) by the generic one (qcom-msm8953)
[ci:ignore-count] [ci:skip-vercheck]
The current OOTB Gstreamer experience on Gnome DEs can be disappointing as
a lot of default codecs and elements are missing. This is often not obvious
for users as Gst in various cases has less optimal fallbacks, easily leaving
the impression that either an app, drivers or hardware are at fault.
Add the most important packages to pmb_recommends so users have a better time.
Notes:
- Many images already ship ffmpeg-libavcodec, so this shouldn't worsen the
legal situation.
- '-bad' is usually already pulled in indirectly while '-good' at least for
GS variants is already required. Both are strongly recommended for apps
like Showtime, Snapshot and many more mobile-friendly apps from the
ecosystem.
- '-bad' really isn't bad any more these days and various elements in it
are used by default if available. That is, many elements there should have
long moved to '-good'.
This was done in 7 steps:
* prepare by running pmbootstrap kconfig migrate
* fix up kconfig category:uefi
* fix up kconfig category:zram
* fix up kconfig category:default
* fix up kconfig category:default (NULL_TTY)
* fix up kconfig category:input
* bump pkgrels
[ci:skip-build]
[ci:ignore-count]
Robert Mader