Is there a possibility to exclude plymouth packages from build and if so how to do that ?
1 Like
what a coincidence 
I am right now looking at a build where I did exactly that.
Give it a few minutes and I know.
EDIT:
Create a copy of the profile you want to build e.g. xfce - xfce profile is used as example throughout this comment - you can of course do this with any of the existing profiles.
Navigate into your iso-profiles folder - it should look like this
[main-devel → fhdk-devel U:1 ?:2] $ tree . -L 1
.
├── community
├── manjaro
├── oem
├── README.md
├── repo_info
└── shared
Create a new folder - e.g. my-editions
mkdir my-editions
Then copy your chosen edition e.g. xfce from the manjaro folder to the my-editions folder.
Due to the way the buildiso script works it is very important that you chose a unique name because there cannot be two profiles with the same name even though they live in separate folders.
cp -R manjaro/xfce/ my-editions/my-xfce
You should now have a structure similar to this
[main-devel → fhdk-devel U:1 ?:3] $ tree . -L2
.
├── community
│ ├── cinnamon
│ └── i3
├── manjaro
│ ├── architect
│ ├── bladebook
│ ├── gnome
│ ├── gnome-next
│ ├── grub
│ ├── kde
│ ├── kde-dev
│ ├── kde-test
│ ├── netinstall
│ ├── nxd
│ └── xfce
├── my-editions
│ └── my-xfce
├── oem
│ ├── beelink-oem-gnome
│ ├── beelink-oem-kde
│ ├── gaming-oem-kde
│ ├── generic-oem-gnome
│ ├── generic-oem-kde
│ ├── generic-oem-plasma
│ ├── generic-oem-xfce
│ ├── infinitybookpro-oem-kde
│ ├── infinitybookpro-oem-xfce
│ ├── minisforum-oem-kde
│ ├── slimbook-creative
│ ├── slimbook-hero
│ ├── starlabs-oem-gnome
│ ├── starlabs-oem-kde
│ └── starlabs-oem-xfce
├── README.md
├── repo_info
└── shared
├── manjaro
├── oem
├── Packages-Desktop
├── Packages-Live
├── Packages-Live-Sponsor
├── Packages-Live-Xorg
├── Packages-Mhwd
├── Packages-Root
└── profile.conf.example
In the new my-editions/my-xfce folder edit the file Packages-Desktop and comment the two lines referencing plymouth and save the file
#plymouth
#plymouth-theme-manjaro
Edit the file profile.conf, find line custom_boot_args=('splash') and change it to custom_boot_args=('') and save the file.
Then you can build the profile - following the example profile name my-xfce
buildiso -p my-xfce -k linux618 -b stable -f
7 Likes
Thanks very much linux-aarhus.
I’ll build a fresh iso tomorrow
I moved your question to a separate topic - so that others having a similar question might find it.
I also clarified the instructions a bit, be sure to revisit - happy building … 
Can confirm the build went fine so again. thanks for sharing your usefull information (over the years). Much appreciated !
With the fresh iso made an “architect” like install and … no plymouth stuff.
Hope somehow this information will also come to the wiki
after the cli made a calamares install and noticed plymouth packages.
Could it be calamares configuration installs plymouth packages ?
sudo pacman -Ss plymouth | grep installed
extra/plymouth 26.134.222-2 [installed]
extra/plymouth-kcm 6.6.5-1 (plasma) [installed]
1 Like
I see you have built the kde profile.
The package plymouth-kcm will pull plymouth as dependency.
As I used the xfce as example I didn’t think there could be other packages that pulled plymouth as requirement.
no problem … a removal of these packages is a few seconds work.
In $HOME/iso-profiles/my-editions/my-kde/Packages-Desktop i noticed the plymouth-kcm in the applications section. i # that now building an unstable.
Will give it a try on a default installation.
After the default installation checked if there were plymouth packages. There were none so imho # the plymouth-kcm in the application section worked with the two other plymouth packages # out.
Mod edit: Consecutive posts merged.
1 Like