Currently the ebuild installs the skeleton files directly
into the ebuild's doc directory. In 0.9.0-r5 the intention
was installing them into a skels folder (although this was not
done correctly).
Replace the sed rules so that the skeleton files are installed
into the skel folder. This will be cleaner if for some reason
nftables adds further documentation on the future. It is also
easier to perform this change now than once we stabilize.
Bug: https://bugs.gentoo.org/671254
Signed-off-by: Francisco Blas Izquierdo Riera (klondike) <klondike@gentoo.org>
Package-Manager: Portage-2.3.76, Repoman-2.3.11
Signed-off-by: Matthew Thode <prometheanfire@gentoo.org>
When the new scripts supporting atomic updates on modern kernels
where introduced, usage of the new scripts was controlled by the
modern_kernel USE flag.
QA has requested that we avoid using underscores on USE flags as
they are a reserved character.
Rename the modern_kernel USE flag to modern-kernel to address
this issue.
Closes: https://bugs.gentoo.org/694838
Signed-off-by: Francisco Blas Izquierdo Riera (klondike) <klondike@gentoo.org>
Package-Manager: Portage-2.3.76, Repoman-2.3.11
Signed-off-by: Matthew Thode <prometheanfire@gentoo.org>
This version features the change that it does install device tree files.
Package-Manager: Portage-2.3.66, Repoman-2.3.16
Signed-off-by: Andrey Utkin <andrey_utkin@gentoo.org>
This version features the change that it does not install device tree
files.
Package-Manager: Portage-2.3.66, Repoman-2.3.16
Signed-off-by: Andrey Utkin <andrey_utkin@gentoo.org>
Upstream git repo provides binaries of two natures in a single
repository:
* boot firmware files;
* prebuilt kernel files.
boot/*.dtb, boot/overlays/ belong to kernel, not boot firmware.
But for historical reasons, these files were installed by
sys-boot/raspberrypi-firmware package rather than
sys-kernel/raspberrypi-image, which would be more correct.
The problem with this is that users of kernels different than
sys-kernel/raspberrypi-image need to install different files into these
locations. This means such people have to avoid using
sys-boot/raspberrypi-firmware package completely.
A blocker dependency on old sys-boot/raspberrypi-firmware versions is
added to protect from a situation when just raspberrypi-image is being
upgraded, and a package manager ends up with a file collision during
installation phase.
Package-Manager: Portage-2.3.66, Repoman-2.3.16
Signed-off-by: Andrey Utkin <andrey_utkin@gentoo.org>
Upstream git repo provides binaries of two natures in a single
repository:
* boot firmware files;
* prebuilt kernel files.
boot/*.dtb, boot/overlays/ belong to kernel, not boot firmware.
But for historical reasons, these files were installed by
sys-boot/raspberrypi-firmware package rather than
sys-kernel/raspberrypi-image, which would be more correct.
The problem with this is that users of kernels different than
sys-kernel/raspberrypi-image need to install different files into these
locations. This means such people have to avoid using
sys-boot/raspberrypi-firmware package completely.
A blocker dependency on old sys-kernel/raspberrypi-image versions is
added to protect from a situation when just raspberrypi-firmware is
being upgraded, and the machine ends up not having device tree files.
Upgrading to a new version may cause a disruption if the user doesn't
use sys-kernel/raspberrypi-image but still relies on device tree files
installed by raspberrypi-firmware package. This will be dealt with by a
news item. A special USE flag for smooth transition of such users is
considered an overkill, on presumption that this package is not
massively popular.
Package-Manager: Portage-2.3.66, Repoman-2.3.16
Signed-off-by: Andrey Utkin <andrey_utkin@gentoo.org>
in versions prior to 1.0 there was a configuration parameter for gnome
but in cmake build it does not exist anymore. the only occurance
of libgnomevfs2 is in ${S}/snap/snapcraft.yaml which seems to be used
for bulding installer for mac os.
Package-Manager: Portage-2.3.80, Repoman-2.3.19
Signed-off-by: Miroslav Šulc <fordfrog@gentoo.org>