Add a USE flag for Plasma's Welcome Center?

ruby_R53

Really, the only package that depends on it is plasma-meta itself. If the user is already familiar with KDE Plasma, it becomes useless.

If I wanna remove it, that means I'll have to uninstall plasma-meta as well and then I'll have to manually select all the other packages I want to keep so that they don't get removed in a future --depclean.

I know I could emerge plasma-desktop or kdecore-meta instead but I don't wanna bother manually installing all the other packages I need. It would be a lot more efficient if plasma-meta had a USE flag for installing the Welcome Center instead.

rab0171610 · Guru Joined: 24 Dec 2022 Posts: 463

I have the menu entry in the app menu set to hidden. If you don't want to do all the things you mentioned in your post to avoid it, then I'd suggest you do the same and then forget about it. The other option is to create an entry for it in package.provided. It is generally recommended to avoid that option unless you know what you are doing.

ruby_R53 · Posted: Tue Jan 28, 2025 5:40 pm Post subject:

i see, guess i can use the package.provided approach for now

rab0171610 · Guru Joined: 24 Dec 2022 Posts: 463

I have one entry for package.provided. My general suggestion is to keep the entries limited to non-existent. Make sure you don't forget about them in case there are issues or unexpected behavior. Comment them out and see if that fixes the problem before filing bug reports or asking for help. In this case, I don't see that it would do much harm as the program is very basic, independent and non-essential. However you have to provide a package version number which means you would have to update the entry indefinitely. When taking that into consideration, the best option is just to hide the menu entry with kmenuedit and forget about it. It really doesn't take up space and is non-intrusive.

ruby_R53 · Posted: Tue Jan 28, 2025 7:15 pm Post subject:

yeah that makes sense, plasma doesn't get updates that often so it's not a big deal

rab0171610 · Guru Joined: 24 Dec 2022 Posts: 463

Hypothetically, it should work indefinitely with any package version, even one from years back or an invalid version number that never existed. Possibly even <category/packagename>-0 or <category/packagename>-1.

ruby_R53 · Posted: Tue Jan 28, 2025 7:41 pm Post subject:

interesting, i wonder why you can't just use a * for all versions instead

Hu · Administrator Joined: 06 Mar 2007 Posts: 23062

package.provided is for assuring Portage that the identified package is present, and that Portage therefore does not need to install it. You cannot pre-install all possible versions of a package, so you cannot assure Portage that all versions are present.

ruby_R53 · Posted: Tue Jan 28, 2025 9:46 pm Post subject:

ohh that makes sense now x)