You are not logged in.
TUs from certain derivates updated their own repos, but "forgot" about Arch's. Anyway, there's an ongoing effort here:
https://github.com/Eadrom/arch_mate
Fork the repo, build the packages in a chroot, and fix the PKGBUILDs. Then either find a TU to upload them, or ask the packages to be dropped to AUR where you can maintain them.
Last edited by Alad (2016-06-30 08:57:13)
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
Dropping Mate to AUR... Ouch! Summer is coming, so we could be lucky to see Mate 1.14.x in Community before september... When Mate 1.16.0 will be surely released.
Offline
Mate 1.16 will be GTK3 only, right? That should at least make things easier from a maintenance point of view.
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
Mate 1.16 will be GTK3 only, right? That should at least make things easier from a maintenance point of view.
Theorically, yes
As I said before, I'm using on a daily basis Mate Desktop 1.15.0 built against gtk3... And it is really good
Offline
Hi folks. Here's an update on my progress.
I'm still working on build testing right now. There's an interesting challenge when using split-package PKGBUILD's on packages that are mutually exclusive once installed. That scenario occurs with MATE because you only want the GTK2 or GTK3 versions of MATE's packages. I think I have that handled using provides() and conflicts() in a slightly different way. I've gotten a new build script from the one I was using the last couple weeks from the previous maintainer of MATE for Arch and it's pretty awesome. It's building the 32 and 64 bit versions of both GTK2 and GTK3 versions of each package properly. The output is also suitable for a custom repo that I can make available until such a time that I can officially update Arch's repo.
Now that I have packages building correctly and able to build upon each other as they build, I have to fix the mutually exclusive dependency issue across all the packages. If all goes well, I'll be able to finish that tonight.
MATE 1.15 is the unstable, development branch for the 1.16 stable release. If I package for 1.15, it'll be super unofficial. I do plan for 1.16 to be GTK3 only. One of the reasons for the split-package pkgbuilds approach for 1.14 is to make the transition to 1.16 super easy.
Thank you for everyone's patience. I know this is taking a while as I sort through all the different problems and things I need to learn as I come across them. Ya'll have been very supportive and I really appreciate it!
Offline
End of the night update. I've hit a roadblock w/ mate-settings-daemon. It's failing to build the i686 GTK3 version. Here's a screenshot of the failures. http://imgur.com/FQXvyRs
I believe this is the relevant bit of code - https://github.com/mate-desktop/mate-se … -manager.c the errors are referencing.
Antergos's PKGBUILD: https://github.com/Antergos/antergos-pa … n/PKGBUILD
Manjaro's PKGBUILD: https://gitlab.com/KlipKyle/mate-pkgbui … 3/PKGBUILD
My PKGBUILD: https://github.com/Eadrom/arch_mate/blo … n/PKGBUILD
Everything up to this point (~1/2 the core MATE packages) will build just fine. I've referenced the Antergos and Manjaro PKBUILD's for this package and there's nothing really obviously different. I've reached out on the MATE IRC and to Martin (previous maintainer), so hopefully I can get some help figuring out where I've gone off the tracks. My C is very rudimentary, which isn't helping to debug this problem. I'm not sure if Antergos/Manjaro just aren't building the 32-bit versions of the package or if they just aren't having the issue I am for some reason (I assume the latter). I wasn't able to find anything from either team talking about this issue.
If anyone is able to help me figure this out, I'd be very thankful! Anyone should be able to replicate problem by spinning up a clean Arch vm, cloning my repo, delete any deprecated folders I've kept around for reference (`rm -rf ./*_deprecated`), and running `./builder.sh -t build` as root.
Offline
Hi folks. Here's an update on my progress.
[progress]
MATE 1.15 is the unstable, development branch for the 1.16 stable release. If I package for 1.15, it'll be super unofficial. I do plan for 1.16 to be GTK3 only. One of the reasons for the split-package pkgbuilds approach for 1.14 is to make the transition to 1.16 super easy.
Thank you for everyone's patience. I know this is taking a while as I sort through all the different problems and things I need to learn as I come across them. Ya'll have been very supportive and I really appreciate it!
I've been using unstable version since Mate 1.13.0 (1.13.1) first by curiosity, then I built 1.14.x on my computer and then 1.15.0/1.15.1.
Everytime using gtk3 and it works great.
By the way, I think that mate 1.16 will be released by next september / october in order to be synced with Ubuntu Mate 16.10... A simple and educated guess
Offline
Hi Everybody,
sorry for my intrusion,
I haven't read all the thread, so probably I lost something.
I would like just to inform you that I installed Mate 1.14 (GTK3) downloading all the mate .pkg from a Manjaro Repo and installed them manually with pacman -U in my Arch Distro.
It's 2 weeks and it is working all properly IMO.
Cheers.
Last edited by CharliePrm88 (2016-07-04 08:53:08)
Offline
Offline
I haven't read all the thread, so probably I lost something.
:-) thank you
Last edited by CharliePrm88 (2016-07-05 11:21:44)
Offline
End of the night update. I've hit a roadblock w/ mate-settings-daemon. It's failing to build the i686 GTK3 version. Here's a screenshot of the failures. http://imgur.com/FQXvyRs
I believe this is the relevant bit of code - https://github.com/mate-desktop/mate-se … -manager.c the errors are referencing.
I can confirm this on x86_64. Did you get in touch with upstream?
edit: you need mate-desktop-gtk3 to build mate-settings-daemon-gtk3. Other -gtk3 packages are likely similar. In other words, as a PKGBUILD must contain all packages required for the build in the global make/depends arrays, and mate-desktop{,-gtk3} conflict, it seems there's no way around separate PKGBUILDs.
Last edited by Alad (2016-07-09 08:21:46)
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
Given the plans for 1.16, which is due out in 2-3 months, and the reports of successful deployment of the GTK3 version of 1.14 and 1.15 on this thread, maybe it would be best to just concentrate on getting the GTK3 version PKBUILDs together? If 1.16 is to be GTK3 only, then I strongly suspect that all the developers focus went there for 1.14 as well anyway. I'm still using the GTK2 version of 1.12, but am happy to switch.
Offline
if people want to try 1.14 and are not afraid of compiling or know what they are doing:
https://github.com/xpander69/mate-archbuilds
MateScript.sh should take care of the build order, but be warned, i might have missed something and im not responsible for system instablities or broken packages.
Have been using mate 1.14 for 2 days now. works great so far. caja has been improved for dark themes, icon text is not black on a black theme anymore, which was the most annoying issue for me.
rest is pretty much same .
Linux Gaming Videos:http://www.youtube.com/user/Xpander666
Offline
Just a note : you can "upgrade" mate-themes to version 3.20.9. There is some more fix, and no need to apply a patch - for firefox ? - on it.
http://pub.mate-desktop.org/releases/themes/3.20/
My homemade version of Mate 1.15.1 is annoyingly stable
Looks like Mate 1.16 will be released sooner than two or three months. Just an educated guess
Offline
My homemade version of Mate 1.15.1 is annoyingly stable
Did you build packages or just run make/make install from a tarball?
My problem with getting away from the package system is that you then become responsible for managing these files, and getting rid of them again to go back to packages will liklely be a pain.
My most experienced DevOps friends avoid writing code like the plague: success is measure by how little new code you have to write. I think a similar principle applies to installing software outside the package system.
Offline
I used 1.12.x PKGBUILDs for gtk3 and adapt them for 1.15.x. So no problems with pacman at all
Offline
Thanks to nicman23 MATE 1.15 is in the AUR.
Offline
Unless it's rename to something like "mate-unstable", it's going to be deleted because it duplicates packages in the official repositories.
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
Installing the nicman23 packages from the AUR worked, although felt a bit like switching to gentoo, as I'm not using yourt. You'll have to bootstrap the install, as some of these mate GTK3 packages have build dependencies on others. Here is the list of packages I needed to duplicate my previous Mate 1.12 GTK2 install:
caja-1.15-gtk3
eom-1.15-gtk3
libmatekbd-1.15-gtk3
libmatemixer-1.15-gtk3
libmateweather-1.15-gtk3
marco-1.15-gtk3
mate-applets-1.15-gtk3
mate-backgrounds-1.15-gtk3
mate-common-1.15-gtk3
mate-control-center-1.15-gtk3
mate-desktop-1.15-gtk3
mate-icon-theme-1.15-gtk3
mate-media-1.15-gtk3
mate-menus-1.15-gtk3
mate-notification-daemon-1.15-gtk3
mate-panel-1.15-gtk3
mate-polkit-1.15-gtk3
mate-screensaver-1.15-gtk3
mate-session-manager-1.15-gtk3
mate-settings-daemon-1.15-gtk3
mate-system-monitor-1.15-gtk3
mate-terminal-1.15-gtk3
mate-themes-1.15-gtk3
mate-user-guide-1.15-gtk3
mate-utils-1.15-gtk3
mozo-1.15-gtk3
pluma-1.15-gtk3
mate-common is new, you'll have to build and install this before anything else as most of these packages have a build dependency on this. I also needed to install the following distro packages before some of the above would build:
gtk-doc
intltool
docbook2x
gtksourceview3
gobject-introspection
libwnck3
libunique3
icon-naming-utils
accountsservice
xmlto
xtrans
gtkmm3
vte3
rarian
You'll probably have to uninstall most of the Mate GTK2 packages before proceeding, as most of the GTK3 packages have build dependency on mate-desktop-1.15-gtk3, but this can't be installed because the GTK2 stuff (e.g. caja, pluma, eom, etc.) depends on the 1.12 mate-desktop. I didn't try force installing anything because this is a path of last resort.
Here is a workable but somewhat tedious algorithm for people who don't use yourt: attempt to makepkg each package in order, and whenever you run into a build dependency switch to that package directory, build and install; then go back. Kind of like putting things on a stack and popping them off again, and you will end up with a secondary iteration when you get to mate-panel; also a build dependency for several mate packages. The path of least resistance is yourt, or similar tool, but these notes should be helpful to stubborn Arch users like myself who don't want AUR packages updated automatically.
Hope this helps someone!
Last edited by pgoetz (2016-07-13 22:41:57)
Offline
Here is a workable but somewhat tedious algorithm for people who don't use yourt: attempt to makepkg each package in order, and whenever you run into a build dependency switch to that package directory, build and install; then go back. Kind of like putting things on a stack and popping them off again, and you will end up with a secondary iteration when you get to mate-panel; also a build dependency for several mate packages. The path of least resistance is yourt, or similar tool, but these notes should be helpful to stubborn Arch users like myself who don't want AUR packages updated automatically.
https://bbs.archlinux.org/viewtopic.php?id=214473
git clone https://github.com/nicman23/arch_mate
cd arch_mate
# vim (...)
find -name PKGBUILD -execdir mksrcinfo \;
aurbuild -a <(aurqueue *) -c -d custom -r /var/cache/pacman/custom -p /var/cache/pacman/custom
Builds all mate packages in an nspawn container in one go, without needing an order file. Then install:
sudo pacman -Syu mate-panel
Note that you'll have to put the local repository above [community], or specify the repo name before the packages.
Last edited by Alad (2016-07-14 08:32:42)
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
git clone https://github.com/nicman23/arch_mate cd arch_mate # vim (...) find -name PKGBUILD -execdir mksrcinfo \; aurbuild -a <(aurqueue *) -c -d custom -r /var/cache/pacman/custom -p /var/cache/pacman/custom
Builds all mate packages in an nspawn container in one go, without needing an order file. Then install:
Wow, thanks for that helpful hint. A couple of follow up questions:
Presumably mksrcinfo is part of the aurutils package?
what does the line
# vim (...)
mean?
Offline
mksrcinfo is from community/pkgbuild-introspection and does the same thing as `makepkg --printsrcinfo > .SRCINFO`
Future versions of mksrcinfo will in fact act as a wrapper for makepkg.
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
mksrcinfo is from community/pkgbuild-introspection and does the same thing as `makepkg --printsrcinfo > .SRCINFO`
Now to send patches to makepkg, so --printsrcinfo is as fast as mksrcinfo ...
what does the line
# vim (...)
mean?
Well, you're still downloading pkgbuilds from a third party. The comment line means you should check and edit them beforehand with an editor of choice.
Last edited by Alad (2016-07-14 20:12:02)
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
mksrcinfo is from community/pkgbuild-introspection and does the same thing as `makepkg --printsrcinfo > .SRCINFO`
Now to send patches to makepkg, so --printsrcinfo is as fast as mksrcinfo ...
I think most of that comes from having to source all of libmakepkg.
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline