On Fri, 4 Aug 2017 17:36:12 +0800
Ben Woods <woods...@gmail.com> wrote:

> Hi FreeBSD Xfce team,

Hi Ben,

> 
> I am a relatively new ports committer that uses Xfce as my main desktop
> environment.
> 
> I have noticed there are a number of Xfce bugs and regular updates
> required. It appears to be a relatively high burden to keep Xfce up-to-date
> and functional on FreeBSD. The more hands, the better.
> https://lists.freebsd.org/pipermail/freebsd-xfce/2017-July/001852.html
> 
> I would like to offer to help, with the spare time I have (which isn't a
> huge amount unfortunately). If you will have me, could someone please
> explain the development process used by the team, and the policy / approval
> process for updating and fixing ports?

It's very simple, commit only stable releases (currently it's full transition 
between Gtk2 and Gtk3, so there're lot of unstable releases 4.13.x, 0.11.x).

Status of opened bugs are available here [1].

Tumbler must be upgraded (head and especially quarterly branch, because 0.1.32 
fixes memory leaks + others bugs especially typos). You can see my previous 
message [2], where I explain difference between 0.2.0 and 0.1.32 releases.

I'm waiting review and commit for support of libgarcon-gtk3 in Mk/Uses/xfce.mk 
[3].

About Mk/Uses/xfce.mk, gtk3 argument is a temporary argument, because in the 
next 4.14 release, core components, applications and plugins will switch to 
Gtk3. But today we need Gtk3 support in xfce4-panel or libxfce4ui (for 
applications).

Currently only panel plugins are Gtk3 ready. Some applications are in 
transition or not compatible with Gtk3 >= 3.20 (especially Mousepad, there're 
lots of warning and so on). 

Beside review D10327 [4] does not mention conflict between flavor (for 
Mousepad, Midori, xfce4-taskmanager it's same binary but with differents 
toolkits Gtk2 and Gtk3).

2 bugs must be closed (and additional flags are inadequate):
- bug #218941, reporter says everything is fine, so  Kubilay Kocak (koobs@) 
should read comment instead to add additional flags
- bug #219337, since the 0.8.6 release, almost features are implemented (again, 
additional flags are not needed)
It's very boring to be spamming by someone who does not follow the project. 

I'm also working on devel of xfdashboard (0.7.3) because I noticed odd 
behavior. Now users can use their own theme (or can modify the default theme), 
so we can ship "broken" package (or not) and display a message, which explains 
how to have working port. 

In my repository, ports in the 4.13 tags are not compatible with the official 
ports tree (xfce4-panel and xfwm4 are very instable and often crashed).

Regards,

[1] https://app.assembla.com/spaces/xfce4/subversion/source
[2] https://lists.freebsd.org/pipermail/freebsd-xfce/2017-July/001829.html
[3] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219334
[4] https://reviews.freebsd.org/D10327


> 
> Regards,
> Ben
> 
> --
> From: Benjamin Woods
> woods...@gmail.com
> _______________________________________________
> freebsd-xfce@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-xfce
> To unsubscribe, send any mail to "freebsd-xfce-unsubscr...@freebsd.org"


-- 
olivier
_______________________________________________
freebsd-xfce@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xfce
To unsubscribe, send any mail to "freebsd-xfce-unsubscr...@freebsd.org"

Reply via email to