dear james777:Here is someone working on GNOME 46 / 47 for FreeBSD.
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...
Y'know, I'd suggest sticking to what the FreeBSD User Handbook can walk you through. That's what these Forums are for.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.
And to cope with ports, Porter's Handbook is must-read.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.
Umm... T-Aoki , I feel I have to disagree a bit with you here...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.
sorry :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.
Well, there's a lot more to a successful install on FreeBSD than just cloning a git repo and runningsorry :
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
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.now, i plan gnome and awesome double GUI. just for a stable desktop to work. thanks.Well, there's a lot more to a successful install on FreeBSD than just cloning a git repo and runningmake install
. If you runmake 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.
Dear t-aoki: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.
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 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.
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.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).I myself dumped on Wayland/sway. Less code - less errors.
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.
Dear astyle :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.