GNOME maintenance

Hi all
I don't want to start any controversy, but I have a simple question:
- is gnome still under development/maintenance for freebsd?

Thanks
 
Gnome is slowly becoming more and more depend on Linux specific functionality, which makes it more and more difficult to port and have an actual functional Gnome desktop on FreeBSD. I've given up on Gnome a long time ago. Last version I used was 2.32 I think.
 
I see, me running 42 but switched to xfce4 2 days ago.. unfortunately
Anyways, xfce is faster but I am missing gnome
 
ok, this thread can be closed.
it seems no one is interested in GNOME unfortunately
not even the guys behind FreeBSD ports
 
I've just submitted an update for GNOME 47, unfortunately bugzilla and phabricator (review.freebsd.org) refuse to take my patch (it is big), so it is available here.

Enjoy!

dear olivierd :
thanks for your project . i am new guys. can you show me how to install gnome47 in freebsd14.2 with step by step ? . i don't know how to install it. thanks.
 
I've just submitted an update for GNOME 47, unfortunately bugzilla and phabricator (review.freebsd.org) refuse to take my patch (it is big), so it is available here.

Enjoy!
Maybe split your patch up into a few smaller files? Like, organize them by topic so that it's easier to keep track of which patch fixes what...
 
dear olivierd :
thanks for your project . i am new guys. can you show me how to install gnome47 in freebsd14.2 with step by step ? . i don't know how to install it. thanks.
Y'know, I'd suggest sticking to what the FreeBSD User Handbook can walk you through. That's what these Forums are for.

Asking someone who just submitted a patch (and already knows that the submitted work has issues with the production pipeline) to immediately help with installation - that is kind of too much to ask for.

I'm on the KDE side of things, as a rank-and-file user who is NOT a dev. I know how to compile my way into KDE, but applying a patch to a port correctly is something I only learned how to do last year. There's a LOT to learn just from the FreeBSD User Handbook. fff2024g , stick to the Handbook until you have learned how to get info from it, and can achieve success reliably from following the steps outlined in there.
 
Y'know, I'd suggest sticking to what the FreeBSD User Handbook can walk you through. That's what these Forums are for.

Asking someone who just submitted a patch (and already knows that the submitted work has issues with the production pipeline) to immediately help with installation - that is kind of too much to ask for.

I'm on the KDE side of things, as a rank-and-file user who is NOT a dev. I know how to compile my way into KDE, but applying a patch to a port correctly is something I only learned how to do last year. There's a LOT to learn just from the FreeBSD User Handbook. fff2024g , stick to the Handbook until you have learned how to get info from it, and can achieve success reliably from following the steps outlined in there.
And to cope with ports, Porter's Handbook is must-read.
Even for non-committer like me, parts of Committer's Guide could help understanding how it goes.
I'm still repeatedly reading both.
 
And to cope with ports, Porter's Handbook is must-read.
Even for non-committer like me, parts of Committer's Guide could help understanding how it goes.
I'm still repeatedly reading both.
Umm... T-Aoki , I feel I have to disagree a bit with you here...

The way I see it, Porter's Handbook is only needed if one actually needs info beyond the basic overview provided by the User Handbook. And I just don't get the impression that fff2024g is ready to go beyond the User Handbook at this point. I guess this is just me playing the devil's advocate against information overload.

Well, there are benefits to knowing that User Handbook only provdes a basic overview of FreeBSD's capabilities, and that other materials go more in-depth on selected topics.

The way I see it, a taste of success is one of the best ways to sell people on learning how to use FreeBSD. :)
 
Y'know, I'd suggest sticking to what the FreeBSD User Handbook can walk you through. That's what these Forums are for.

Asking someone who just submitted a patch (and already knows that the submitted work has issues with the production pipeline) to immediately help with installation - that is kind of too much to ask for.

I'm on the KDE side of things, as a rank-and-file user who is NOT a dev. I know how to compile my way into KDE, but applying a patch to a port correctly is something I only learned how to do last year. There's a LOT to learn just from the FreeBSD User Handbook. fff2024g , stick to the Handbook until you have learned how to get info from it, and can achieve success reliably from following the steps outlined in there.
sorry :
i have git clone this project ,and make install clean. it's not work. so i just want to know how to install gnome47 to freebsd14.2 .it's not want to know how to patch ......thanks
 
sorry :
i have git clone this project ,and make install clean. it's not work. so i just want to know how to install gnome47 to freebsd14.2 .it's not want to know how to patch ......thanks
Well, there's a lot more to a successful install on FreeBSD than just cloning a git repo and running make install. If you run make install in a port directory, you'll get better results. So, you can try reading the Porter's Handbook to get an idea of just how complex it gets. Even with KDE, the Porter's Handbook has a special section for that. The Porter's Handbook probably has a special section for GNOME, as well.

Play with that stuff in a VM, and be ready to mess up your system to the point of needing a complete reinstall a few times over. GNOME does have a lot of details to line up before you can install from source - especially patched source. Especially on FreeBSD.
 
Well, there's a lot more to a successful install on FreeBSD than just cloning a git repo and running make install. If you run make install in a port directory, you'll get better results. So, you can try reading the Porter's Handbook to get an idea of just how complex it gets. Even with KDE, the Porter's Handbook has a special section for that. The Porter's Handbook probably has a special section for GNOME, as well.

Play with that stuff in a VM, and be ready to mess up your system to the point of needing a complete reinstall a few times over. GNOME does have a lot of details to line up before you can install from source - especially patched source. Especially on FreeBSD.
now, i plan gnome and awesome double GUI. just for a stable desktop to work. thanks.
 
If you know and OK with GNOME2 interfaces, x11/mate would be your friend.
It was forked from GNOME2 and kept on maintained. Application names are changed not to confict with (at the moment) GNOME3 and some apps are dropped due to quite limited resources, as far as I know.
 
If you know and OK with GNOME2 interfaces, x11/mate would be your friend.
It was forked from GNOME2 and kept on maintained. Application names are changed not to confict with (at the moment) GNOME3 and some apps are dropped due to quite limited resources, as far as I know.
Dear t-aoki:
thanks. i just want to got a simple GUI for daily work in freebsd14.2 . so i don't need a complex gUI, just one rule : stable.... about 2 weeks ago, i have running pkg upgrade , so gnome has been removed . now i have used awesome . thanks.
 
GNOME is connected with systemd. Probably so. This is already history. In connection with the recent plague, after which all the lush and bloated X-oriented DE fell, I myself dumped on Wayland/sway. Less code - less errors.
 
Dear t-aoki:
thanks. i just want to got a simple GUI for daily work in freebsd14.2 . so i don't need a complex gUI, just one rule : stable.... about 2 weeks ago, i have running pkg upgrade , so gnome has been removed . now i have used awesome . thanks.
Yeah, looks likethe pkg(8) debacle has claimed yet another documented victim. Do a clean reinstall, and use ports, rather than pkg. FreeBSD User Handbook is your friend in getting things to work smoothly - if you follow directions exactly.
 
astyle, It is good idea! I will split my patch for better re-use.

fff2024g, Avoid to clone my repository, because some ports are not in this one. Use directly my patch git apply 0001-x11-gnome-Update-to-47.patch. I have shell script which clones, merges, but currently it is useless. I need to write a good documentation.

Beastie7, GNOME depends mainly of systemd (we sometimes find logind support). ConsoleKit and logind are pretty close (to the DBus interface), so it is easy to find an equivalent.

Even though I have activated wayland support everywhere, only Xorg session is functional. If we want wayland, we need to rewrite patches in x11/gdm and x11-wm/mutter. It takes time.

Just for record:
x11/gnome-shell-extensions looks like traditional desktop found in GNOME2 (a screenshot), but it based on mutter and gnome-shell.
 
I myself dumped on Wayland/sway. Less code - less errors.
Sway/wlroots has a considerable amount of code running due to the fact that it has to ship much of the Xorg backend with it (*and* currently an Xorg frontend as Xwayland due to much software still being X11-only).
This is also why, when it crashes due to error, it terminates your entire graphical session which is not ideal.

Xorg and i3 (if you like Sway) is a better design because it separates the UI system from the display system. One could even say that this separation is a more "modern" approach. A crash in the WM doesn't take down the display and all programs running in it.
 
Yeah, looks likethe pkg(8) debacle has claimed yet another documented victim. Do a clean reinstall, and use ports, rather than pkg. FreeBSD User Handbook is your friend in getting things to work smoothly - if you follow directions exactly.
Dear astyle :
thanks for your help . i am working in china , so we can't use ports to install any app. the GOV block most internet site. that cause much more problem. thanks
 
Back
Top