Package Details: plymouth-git 24.004.60.r88.ga0e8b6cf-1

Git Clone URL: https://aur.archlinux.org/plymouth-git.git (read-only, click to copy)
Package Base: plymouth-git
Description: Graphical boot splash screen (git version)
Upstream URL: https://www.freedesktop.org/wiki/Software/Plymouth/
Licenses: GPL-2.0-or-later
Conflicts: plymouth
Provides: plymouth
Submitter: PirateJonno
Maintainer: Taijian
Last Packager: Taijian
Votes: 275
Popularity: 0.42
First Submitted: 2009-05-02 09:53 (UTC)
Last Updated: 2024-12-20 00:13 (UTC)

Required by (174)

Sources (6)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 51 Next › Last »

michaldybczak commented on 2023-04-02 09:08 (UTC)

@Taijian, while I agree that AUR is for Arch packages, the comparison you made are not fully accurate. 1. First, Arch is not a singular distro like in the past but a base for a variety of distros, just like Debian is the base for various spin-offs. Looking on AUR as something exclusive to Arch only is just ignorant and arrogant. 2. Second, in this particular case, the PKGBUILD adds additional instructions that made it reliable on packages from Arch repos only. This instruction is not necessary at all, it should be optional. The package plymouth-git will work for all Arch based distros, but the added option made it exclusive and problematic. 3. While I agree that Arch stands in the name of AUR, this addition is unnecessary. It's exactly like Apple making everything they can to make your life harder and exclude every third parties. They have financial incentive to do so, but the only incentive to make an AUR package reliant on Arch repos and files only is just arrogance and egoism, in the best case, it's just ignorant. 4. This is the AUR package maintainer right to do what he desires with the package, it's open source after all and, I assume, the license of plymouth allows it. However, if he alters the base package, it should be reflected in the name. So that is my last problem. You either provide plymouth-git or some personal spin-off. If you know that the package is modified, you are warned and can check what the modifications were about. If you say you provide the base package while you are not, it's just a bad practice and abuse of the AUR customs.

Taijian commented on 2023-04-01 10:19 (UTC)

@Anagastes: I think you have a pretty serious misconception here about what AUR PKGBUILDs are and are not.

A PKGBUILD is a recipe for building a particular package. It lists a number of ingredients in the depends= and makedepends= arrays and then has instructions on how to proceed with these ingredients towards creating a functional and installable package.

In listing these ingredients, it does assume that you will actually be using the exact same ingredients, because - if you are not - then the rest of the instructions might not work for you. Now, because this is the AUR, as in Arch User Repository, the assumption is that you will be using the packages (ingredients) from the Arch repos - and then the recipes will work.

You can of course make the choice for yourself that you do not want to use Arch, but some other distro. Totally fine. But that is like taking a recipe from an egg-lovers foodie blog and then complaining that it does not work or taste well, because you choose to only frequent a store that sells avocados instead of eggs. Well yes, it that case certain adjustments may be necessary to make all those recipes work for you that assume that you have easy access to eggs. And, with a bit of tinkering and improvisation, I am sure some very nice dishes can be prepared with avocados instead of eggs. And that is a very valid life choice.

The difference of opinion between you and me seems to be in whose responsibility it should be to do the tinkering and the improvisation. And I happen to believe that it should be you, who refuses to use the nice eggs I put in my recipe. Of course I might try to accomodate you and work out a way to do things without eggs - or avocado OR egg, alternatively. But then tomorrow someone might decide that they what to switch all instances of flour for nutmeg. Or brussel sprouts. See the problem?

If you are not using Arch, the authors of AUR PKGBUILDs have zero way a knowing what kinds of packages are installed on your system or get pulled in via dependencies. So you are of course free to use the AUR, but please do not try to make other people responsible for your choices.

Now, if you do want to make a positive contribution and have worked out to make plymouth-git work for your distro of choice, why not type up a nice summary of what you did and either post it here (we might even get it pinned) or put it in your distros wiki for all to see!

Anagastes commented on 2023-03-31 19:21 (UTC)

Sorry, but this is also 100% incomprehensible to me. Arch packages should be universally usable for distris that are based on Arch. And not be bound to a fixed logo!

I have now also had to adjust the PKGBUILD and manually removed these logos everywhere. Sorry... but what's the point, with this you destroy many Distris at once.

Taijian commented on 2023-03-31 17:32 (UTC) (edited on 2023-03-31 17:32 (UTC) by Taijian)

@yloose Yeah, and if you read the post-upgrade message displayed after updating the package, then you already know what to do and why :)

yloose commented on 2023-03-31 16:56 (UTC) (edited on 2023-03-31 17:06 (UTC) by yloose)

@gnunn Yeah, after updating this package, mkinitcpio reports that the plymouth-encrypt hook can not be found.

gnunn commented on 2023-03-31 16:41 (UTC)

Has anyone had an issue with the last update with luks and plymouth-encrypt not prompting for a password? When I boot my laptop it just sits there with the laptop logo and a spinning wheel. Pressing escape doesn't show anything and there doesn't appear to be a way to enter the luks password. I ended up having to boot a USB stick with Arch and remove plymouth and replace plymouth-encrypt with encrypt in mkinitcpio.conf in order to be able to boot again.

michaldybczak commented on 2023-03-30 20:11 (UTC)

I've been using plymouth-git for years and this is the first time I came across such an issue. I checked all the filex and it turned out, that even when I removed all the parts with arch images, it still brought it up from somewhere, although I opened EVERY FILE AND SEARCHED FOR ARCH. Anyway, the easiest part was just to add those two missing images. All of that issue was because the script was making plymouth theme for arch. For me useless, because I wouldn't use it anyway.

Taijian commented on 2023-03-30 19:12 (UTC)

@michaldybczak: notabug/wontfix

If you try to install an Arch package on a non-Arch system, the onus is on you, as a user, to adapt the PKGBUILD to your needs. On Arch systems, the file in question is provided by 'filesystem', feel free to edit said line in the PKGBUILD to suit your needs. Just be aware that the 'archlinux-logo.png' file is also referenced in 'plymouth.initcpio_install', so you might run into problems down the line anyway, if it is missing on your system.

michaldybczak commented on 2023-03-30 18:23 (UTC) (edited on 2023-03-30 18:25 (UTC) by michaldybczak)

Won't build: INFO: calculating backend command to run: /usr/bin/ninja -C /mnt/home-hdd/build/plymouth-git/src/build Error reading file "/usr/share/pixmaps/archlinux-logo-text-dark.svg": Error opening file /usr/share/pixmaps/archlinux-logo-text-dark.svg: No such file or directory ==> ERROR: There is error in build(). Aborting... Looks like the build is expecting arch logo, but not all Arch based systems have it. It is either a bug in build or bug in git expecting plymouth to be installed only on Arch...

ceg commented on 2022-11-29 18:13 (UTC) (edited on 2022-11-29 18:13 (UTC) by ceg)

Segfault probably got fixed with this issue: https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/196

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 51 Next › Last »