| View previous topic :: View next topic |
| Author |
Message |
Spanik
Veteran
Joined: 12 Dec 2003
Posts: 1062
Location: Belgium
|
 Posted: Sat Apr 12, 2025 2:29 pm Post subject: lxde-meta masked (solved) |
 |
|
I wanted to emerge lxde. But it looks like that every package is masked with ~amd64. Is there a way to unmask lxde-meta as a whole; with every package inside it? Because right now it is each time a run with "emerge --pretend lxde-meta" and then adding a file to /etc/portage/package.accept.keywords. There has to be a simpler way.
_________________
Expert in non-working solutions
Last edited by Spanik on Mon Apr 14, 2025 2:44 pm; edited 1 time in total |
|
| Back to top |
|
 |
szatox
Advocate
Joined: 27 Aug 2013
Posts: 3605
|
| Posted: Sat Apr 12, 2025 2:44 pm Post subject: |
|
|
One way is to set ACCEPT_KEYWORDS=~amd64 and move the whole system to testing. It is actually quite reliable.
Anyway, you've been here long enough you should already know --autounmask-write. Is there any problem with it? Hmm... Maybe --pretend is getting in your way. Use --ask instead.
_________________
Make Computing Fun Again |
|
| Back to top |
|
|
Spanik
Veteran
Joined: 12 Dec 2003
Posts: 1062
Location: Belgium
|
| Posted: Sat Apr 12, 2025 7:46 pm Post subject: |
|
|
| szatox wrote: | One way is to set ACCEPT_KEYWORDS=~amd64 and move the whole system to testing. It is actually quite reliable.
Anyway, you've been here long enough you should already know --autounmask-write. Is there any problem with it? Hmm... Maybe --pretend is getting in your way. Use --ask instead. |
Thanks, I'll try. Used it once long ago and it left a trail of stuff I didn't know what to do with. Never used it after that.
While I'm here a long time, I'm a "user". I'm really not into programming, the finer points of all possible options etc. I can get Gentoo installed following the handbook. And after that I get along with some "incantations", a series of terminal commands I gathered over the years. Once those let me down I'm depending on the forum. I really don't understand the more technical points you find on the net using google or another search engine. So when for instance when I do a "make oldconfig" and I get a long list of questions about things I really have no idea what they mean I just go with what is suggested. Likewise, what I find with "eselect news read" is 90% just gibberish to me. It is written by those programming this to others programming (or at least involved in the general linux tree). So when it says "run this command, do that, update this" I just type what is written there. But I don _understand_ what is happening or why.
_________________
Expert in non-working solutions |
|
| Back to top |
|
|
pingtoo
Veteran
Joined: 10 Sep 2021
Posts: 1632
Location: Richmond Hill, Canada
|
| Posted: Sat Apr 12, 2025 8:19 pm Post subject: Re: lxde-meta masked |
|
|
| Spanik wrote: | | I wanted to emerge lxde. But it looks like that every package is masked with ~amd64. Is there a way to unmask lxde-meta as a whole; with every package inside it? Because right now it is each time a run with "emerge --pretend lxde-meta" and then adding a file to /etc/portage/package.accept.keywords. There has to be a simpler way. |
I found this interesting, so do you mind we discuss a bit more in to detail of what you think being difficult?
From your post i presume you have already got lxde-meta packed list of packages in to package.accept_keywords. so in theory a "emerge -av lxde-meta" would just do the right thing. is this not true?
On the other hand I presume doing "ACCEPT_KEYWORDS=~amd64 emerge -av lxde-meta" (assume no packages in /etc/portage/package.accept_keywords just for this conversation) does not meet what you need, can you explain why in this case?
In my mind since you already put necessary packages in to /etc/portage/package.accept_keywords therefor all the hard work already done what is you are looking for? Automatically generate the list for next update? |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 3013
Location: Edge of marsh USA
|
| Posted: Sun Apr 13, 2025 2:42 am Post subject: |
|
|
Add to /etc/portage/package.accept_keywords
| Code: | # As suggested by Ionen do the following:
lxde-base/*
x11-libs/libfm
x11-libs/libfm-extra
x11-misc/pcmanfm |
ADDED: New versions of all of the LXDE components have been added upstream at https://github.com/lxde/releases.
These have been announced to the LXDE mailing list recently beginning in early March. https://sourceforge.net/projects/lxde/lists/lxde-list
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
Spanik
Veteran
Joined: 12 Dec 2003
Posts: 1062
Location: Belgium
|
| Posted: Sun Apr 13, 2025 8:20 am Post subject: Re: lxde-meta masked |
|
|
| pingtoo wrote: | I found this interesting, so do you mind we discuss a bit more in to detail of what you think being difficult?
From your post i presume you have already got lxde-meta packed list of packages in to package.accept_keywords. so in theory a "emerge -av lxde-meta" would just do the right thing. is this not true?
On the other hand I presume doing "ACCEPT_KEYWORDS=~amd64 emerge -av lxde-meta" (assume no packages in /etc/portage/package.accept_keywords just for this conversation) does not meet what you need, can you explain why in this case?
In my mind since you already put necessary packages in to /etc/portage/package.accept_keywords therefor all the hard work already done what is you are looking for? Automatically generate the list for next update? |
Not difficult, just looking for a faster way. There is nothing from lxde on he pc when I started, I just want to try this desktop. So I first searched with "emerge --search lxde" and found that there was a "meta" package. So that looked like what I needed to get the desktop. Next I ran "emerge --pretend ldxe-meta" which told me that it was masked with ~amd64. So I added /etc/portage/package.accept.keywords/lxde-meta. Ran "emerge --pretend lxde-meta" again which told me that lxde-icon-theme was masked. So I added /etc/portage... Then it was lxde-common that was masked.You get the idea, each "emerge --pretend" listed the next package that was masked.
Now normally when I have masked packages it is a single package, at most 2 at the same time. Which isn't an issue, so far there are 6 of such packages listed in /etc/portage/package.accept.keywords over the years I use this pc. But here, as I have no idea how much packages are behind lxde-meta I was looking for another way.
I'm not so keen on the idea of going over to testing as a whole. Maybe --pretend isn't the right option, but I like the info it gives about what is all going to be recompiled, added puled-in, changes in use... I'll try the "ACCEPT_KEYWORDS=~amd64 emerge -av lxde-meta". See where that leads me.
_________________
Expert in non-working solutions |
|
| Back to top |
|
|
szatox
Advocate
Joined: 27 Aug 2013
Posts: 3605
|
| Posted: Sun Apr 13, 2025 11:58 am Post subject: |
|
|
| Quote: | | I'll try the "ACCEPT_KEYWORDS=~amd64 emerge -av lxde-meta". See where that leads me. |
Honestly this looks more risky than moving the whole system.
Anyway, seriously change your dry-runs from --pretend to --ask. It's the same thing when you decide to abort, and will save you time when you decide to continue.
And also emerge sometimes offers you solution to the problems encountered, like flipping use flags and accepting keywords it needs to proceed, so you can just accept the suggested resolution and follow with dispatch-conf [enter] [enter] instead of meticulously handcrafting your own config based on the output printed to the screen.
_________________
Make Computing Fun Again |
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 2271
|
| Posted: Sun Apr 13, 2025 12:28 pm Post subject: |
|
|
| Yes, don't set it temporarily on the command line. It'll introduce very confusing conflicts later. |
|
| Back to top |
|
|
pingtoo
Veteran
Joined: 10 Sep 2021
Posts: 1632
Location: Richmond Hill, Canada
|
| Posted: Sun Apr 13, 2025 2:12 pm Post subject: Re: lxde-meta masked |
|
|
| Spanik wrote: | | pingtoo wrote: | I found this interesting, so do you mind we discuss a bit more in to detail of what you think being difficult?
From your post i presume you have already got lxde-meta packed list of packages in to package.accept_keywords. so in theory a "emerge -av lxde-meta" would just do the right thing. is this not true?
On the other hand I presume doing "ACCEPT_KEYWORDS=~amd64 emerge -av lxde-meta" (assume no packages in /etc/portage/package.accept_keywords just for this conversation) does not meet what you need, can you explain why in this case?
In my mind since you already put necessary packages in to /etc/portage/package.accept_keywords therefor all the hard work already done what is you are looking for? Automatically generate the list for next update? |
Not difficult, just looking for a faster way. There is nothing from lxde on he pc when I started, I just want to try this desktop. So I first searched with "emerge --search lxde" and found that there was a "meta" package. So that looked like what I needed to get the desktop. Next I ran "emerge --pretend ldxe-meta" which told me that it was masked with ~amd64. So I added /etc/portage/package.accept.keywords/lxde-meta. Ran "emerge --pretend lxde-meta" again which told me that lxde-icon-theme was masked. So I added /etc/portage... Then it was lxde-common that was masked.You get the idea, each "emerge --pretend" listed the next package that was masked.
Now normally when I have masked packages it is a single package, at most 2 at the same time. Which isn't an issue, so far there are 6 of such packages listed in /etc/portage/package.accept.keywords over the years I use this pc. But here, as I have no idea how much packages are behind lxde-meta I was looking for another way.
I'm not so keen on the idea of going over to testing as a whole. Maybe --pretend isn't the right option, but I like the info it gives about what is all going to be recompiled, added puled-in, changes in use... I'll try the "ACCEPT_KEYWORDS=~amd64 emerge -av lxde-meta". See where that leads me. |
It appear you misunderstand my points and my apology that I did not make them clear.
I am not asking you actually do those commands. I am trying to understand from your point of view do you know if those command result different from your goal.
I got a different impression this time from your reply. I was under impression that you already got lxde-meta done on your system but would like to seek a better way for next time. Whereas from this time your reply you gave me impression is that lxde-meta is not done yet and you are seeking howto.
So if my impression this time is correct then please ignore my questions and may be follow figueroa suggestion |
|
| Back to top |
|
|
Spanik
Veteran
Joined: 12 Dec 2003
Posts: 1062
Location: Belgium
|
| Posted: Sun Apr 13, 2025 7:21 pm Post subject: |
|
|
| szatox wrote: | | Quote: | | I'll try the "ACCEPT_KEYWORDS=~amd64 emerge -av lxde-meta". See where that leads me. |
Honestly this looks more risky than moving the whole system.
Anyway, seriously change your dry-runs from --pretend to --ask. It's the same thing when you decide to abort, and will save you time when you decide to continue.
And also emerge sometimes offers you solution to the problems encountered, like flipping use flags and accepting keywords it needs to proceed, so you can just accept the suggested resolution and follow with dispatch-conf [enter] [enter] instead of meticulously handcrafting your own config based on the output printed to the screen. |
Ok, thanks for clearing that out a bit. That is what I mean by "being a user". I'm not involved in the deep workings of all this. I just want a working pc with the least work. I admit that Gentoo might not be the best option then, but all those years ago it was the only distro that just worked for me thanks to the very clear handbook. And I stuck with it.
I was always under the impression that --ask was similar to when you do a "make oldconfig", each change you had to say (y/n). That would be fine when you get 10 questions but when you have an update@world and +500 packages and after each package you need to answer... But ok, I'm wrong on that assumption.
So more practical question: I did the "ACCEPT_KEYWORDS=~amd64 emerge -av lxde-meta" thing and from what I understand now I have set myself up for more conflicts later. Which I would like to avoid. Is there a way to make those accept_keywords more permanently? Or is the only option going to testing?
_________________
Expert in non-working solutions |
|
| Back to top |
|
|
asturm
Developer
Joined: 05 Apr 2007
Posts: 9377
|
| Posted: Sun Apr 13, 2025 7:47 pm Post subject: |
|
|
| Spanik wrote: | | szatox wrote: | | Quote: | | I'll try the "ACCEPT_KEYWORDS=~amd64 emerge -av lxde-meta". See where that leads me. |
Honestly this looks more risky than moving the whole system.
Anyway, seriously change your dry-runs from --pretend to --ask. It's the same thing when you decide to abort, and will save you time when you decide to continue.
And also emerge sometimes offers you solution to the problems encountered, like flipping use flags and accepting keywords it needs to proceed, so you can just accept the suggested resolution and follow with dispatch-conf [enter] [enter] instead of meticulously handcrafting your own config based on the output printed to the screen. |
Ok, thanks for clearing that out a bit. That is what I mean by "being a user". I'm not involved in the deep workings of all this. I just want a working pc with the least work. I admit that Gentoo might not be the best option then, but all those years ago it was the only distro that just worked for me thanks to the very clear handbook. And I stuck with it. |
You're saying that basically all the time when shown Gentoo operating *basics*. Which has nothing to do at all with not being a programmer. The forums can't run your systems for you. After all these years, it can be considered help vampirism. |
|
| Back to top |
|
|
GDH-gentoo
Veteran
Joined: 20 Jul 2019
Posts: 1857
Location: South America
|
| Posted: Sun Apr 13, 2025 8:03 pm Post subject: |
|
|
| Spanik wrote: | | I just want a working pc with the least work. |
Then I'd suggest forgetting about LXDE. Insisting on installing it will require you to either:
- Move to testing as szatox suggested, or
- Mix stable and testing.
And both of them go against your goal above.
If you must have LXDE, contrary to other posters' opinion, I would go with b) using a suitable package.accept_keywords, and as many iterations as necessary until I get it right. Although it looks like it would probably end up looking like what figueroa posted.
_________________
| NeddySeagoon wrote: | I'm not a witch, I'm a retired electronics engineer  |
| Ionen wrote: | | As a packager I just don't want things to get messier with weird build systems and multiple toolchains requirements though |
Last edited by GDH-gentoo on Mon Apr 14, 2025 12:32 pm; edited 2 times in total |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 3013
Location: Edge of marsh USA
|
| Posted: Sun Apr 13, 2025 9:17 pm Post subject: |
|
|
I have been running LXDE or portions of LXDE with OpenBox for many years now. It's exactly what I want for a desktop interface. My current setup is just:
OpenBox window manager with the following in ~/.config/openbox/autostart:
| Code: |
# This file was sourced from /etc/xdg/openbox/autostart
#
# These things are run when an Openbox X Session is started.
# You may place a similar script in $HOME/.config/openbox/autostart
# to run user-specific things.
#
# If you want to use GNOME config tools...
#
#if test -x /usr/libexec/gnome-settings-daemon >/dev/null; then
# /usr/libexec/gnome-settings-daemon &
#elif which gnome-settings-daemon >/dev/null; then
# gnome-settings-daemon &
#fi
# If you want to use XFCE config tools...
#
#xfce-mcs-manager &
#
# End of sourced file
numlockx &
setxkbmap -option terminate:ctrl_alt_bksp -option compose:sclk &
lxpanel &
# Commented pcmanfm 6/26/2022
#pcmanfm --desktop &
/home/figueroa/.fehbg &
volumeicon &
orage &
#Note: lxpolkit is a polkit agent required to run pkexec from sys-auth/polkit
lxpolkit &
sleep 3
conky -d -q &
sleep 2
xfce4-screensaver &
pcmanfm -d &
proton-mail-bridge -n & |
Note that orage had been working and would run minimized on the panel, but a couple of months ago, invoking "orage &" just leaves it invisibly running in the background. I can toggle it on or off with "orage -t" but it never goes onto the panel.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
Spanik
Veteran
Joined: 12 Dec 2003
Posts: 1062
Location: Belgium
|
| Posted: Mon Apr 14, 2025 2:44 pm Post subject: |
|
|
| GDH-gentoo wrote: | | Spanik wrote: | | I just want a working pc with the least work. |
Then I'd suggest forgetting about LXDE. Insisting on installing it will require you to either:
- Move to testing as szatox suggested, or
- Mix stable and testing.
And both of them go against your goal above. |
Guess that I didn't express myself well. But from what I get now, then it will be the easiest to go to "testing" and get my search for a desktop done. Then just wipe the system and start clean with that desktop.
I know some of you will say that I do not need to wipe the system but the last 2 months I have been changing so many settings and configs that there must be inconsistencies and contradictions all over the place. Also quite a few of applications that have become unsupported and so on. Reasons enough to go for a clean install.
_________________
Expert in non-working solutions |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 3013
Location: Edge of marsh USA
|
| Posted: Mon Apr 14, 2025 6:18 pm Post subject: |
|
|
Whichever way you turn, know that lxde~ works perfectly on a stable system.
ADDED: BTW, you may want to see my thread here at: https://forums.gentoo.org/viewtopic-t-1119739-highlight-lxde+openbox.html
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
|
Desktop Environments
