Gnome 3.11.1 is out

[cnd]

http://ftp.acc.umu.se/pub/GNOME/teams/releng/3.11.1/versions

MAP: https://wiki.gnome.org/ThreePointEleven/

Also as @mrpdaemon suggested we keep previous (for now 3.10) version in repository to have some kind of stable and development ebuilds here.

## CORE
core:ModemManager:0.7.991:
core:NetworkManager:0.9.8.8:
core:at-spi2-atk:2.11.1:
core:at-spi2-core:2.11.1:
core:atk:2.11.1:
core:atkmm:2.22.7:
core:baobab:3.10.1:
core:cantarell-fonts:0.0.15:
core:caribou:0.4.12:
core:clutter:1.16.0:
core:clutter-gst:2.0.8:
core:clutter-gtk:1.4.4:
core:cogl:1.16.0:
core:dconf:0.18.0:
core:empathy:3.11.1:
core:eog:3.11.1:
core:epiphany:3.10.1:
core:evince:3.11.1:
core:evolution-data-server:3.11.1:
core:folks:0.9.5:
core:gcr:3.10.1:
core:gdk-pixbuf:2.30.0:
core:gdm:3.10.0.1:
core:geocode-glib:3.10.0:
core:gjs:1.38.1:
core:glib:2.39.0:
core:glib-networking:2.38.1:
core:glibmm:2.38.0:
core:gmime:2.6.19:
core:gnome-backgrounds:3.10.1:
core:gnome-bluetooth:3.10.0:
core:gnome-calculator:3.10.1:
core:gnome-contacts:3.10.1:
core:gnome-control-center:3.11.1:
core:gnome-desktop:3.11.1:
core:gnome-dictionary:3.10.0:
core:gnome-disk-utility:3.10.0:
core:gnome-font-viewer:3.10.0:
core:gnome-icon-theme:3.10.0:
core:gnome-icon-theme-extras:3.6.2:
core:gnome-icon-theme-symbolic:3.10.1:
core:gnome-js-common:0.1.2:
core:gnome-keyring:3.10.1:
core:gnome-menus:3.10.1:
core:gnome-online-accounts:3.10.1:
core:gnome-online-miners:3.10.0:
core:gnome-packagekit:3.10.1:
core:gnome-screenshot:3.10.0:
core:gnome-session:3.11.1:
core:gnome-settings-daemon:3.11.1:
core:gnome-shell:3.11.1:
core:gnome-shell-extensions:3.10.1:
core:gnome-system-log:3.9.90:
core:gnome-system-monitor:3.10.1:
core:gnome-terminal:3.10.1:
core:gnome-themes-standard:3.10.0:
core:gnome-user-docs:3.10.1:
core:gnome-user-share:3.10.0:
core:gnome-video-effects:0.4.0:
core:gobject-introspection:1.38.0:
core:grilo:0.2.7:
core:grilo-plugins:0.2.9:
core:gsettings-desktop-schemas:3.10.1:
core:gssdp:0.14.6:
core:gst-plugins-base:1.2.0:
core:gst-plugins-good:1.2.0:
core:gstreamer:1.2.0:
core:gtk+:3.11.0:
core:gtk+:2.24.22:
core:gtk-doc:1.19:
core:gtk-engines:2.20.2:
core:gtkmm:3.10.1:
core:gtksourceview:3.11.1:
core:gucharmap:3.10.0:
core:gupnp:0.20.8:
core:gupnp-igd:0.2.2:
core:gvfs:1.19.1:
core:json-glib:0.16.2:
core:libchamplain:0.12.5:
core:libcroco:0.6.8:
core:libgdata:0.14.0:
core:libgee:0.12.0:
core:libgnome-keyring:3.10.1:
core:libgnomekbd:3.6.0:
core:libgsf:1.14.28:
core:libgtop:2.28.5:
core:libgweather:3.10.1:
core:libgxps:0.2.2:
core:libnotify:0.7.6:
core:libpeas:1.9.0:
core:libqmi:1.0:
core:rest:0.7.90:
core:librsvg:2.40.0:
core:libsecret:0.16:
core:libsigc++:2.3.1:
core:libsoup:2.44.1:
core:libwnck:3.4.7:
core:libzapojit:0.0.3:
core:mm-common:0.9.6:
core:mousetweaks:3.10.0:
core:mutter:3.11.1:
core:nautilus:3.10.0:
core:network-manager-applet:0.9.8.4:
core:pango:1.36.0:
core:pangomm:2.34.0:
core:pygobject:3.11.1:
core:seed:3.8.1:
core:sushi:3.10.0:
core:totem:3.10.1:
core:totem-pl-parser:3.10.0:
core:tracker:0.16.3:
core:vala:0.22.0:
core:vino:3.10.1:
core:vte:0.34.9:
core:yelp:3.10.1:
core:yelp-tools:3.10.0:
core:yelp-xsl:3.10.1:
core:zenity:3.8.0:

## APPS
apps:accerciser:3.8.2:
apps:aisleriot:3.10.1:
apps:anjuta:3.10.0:
apps:bijiben:3.11.1:
apps:brasero:3.8.0:
apps:cheese:3.11.1:
apps:devhelp:3.10.0:
apps:evolution:3.11.1:
apps:file-roller:3.11.1:
apps:five-or-more:3.11.1:
apps:four-in-a-row:3.10.1:
apps:gedit:3.11.1:
apps:glade:3.16.0:
apps:gnome-boxes:3.10.0:
apps:gnome-chess:3.11.1:
apps:gnome-clocks:3.10.1:
apps:gnome-color-manager:3.10.1:
apps:gnome-devel-docs:3.10.1:
apps:gnome-documents:3.10.0:
apps:gnome-getting-started-docs:3.10.1:
apps:gnome-initial-setup:3.10.1.1:
apps:gnome-klotski:3.11.1:
apps:gnome-logs:3.11.1:
apps:gnome-mahjongg:3.11.1:
apps:gnome-maps:3.10.0:
apps:gnome-mines:3.11.1:
apps:gnome-music:3.10.1:
apps:gnome-nettool:3.8.1:
apps:gnome-nibbles:3.11.1:
apps:gnome-photos:3.10.1:
apps:gnome-robots:3.11.1:
apps:gnome-software:3.11.1:
apps:gnome-sound-recorder:3.11.1:
apps:gnome-sudoku:3.11.1:
apps:gnome-tetravex:3.11.1:
apps:gnome-tweak-tool:3.10.0:
apps:gnome-weather:3.10.1:
apps:iagno:3.11.1:
apps:lightsoff:3.11.1:
apps:nautilus-sendto:3.8.1:
apps:nemiver:0.9.4:
apps:orca:3.10.1:
apps:polari:3.11.1:
apps:quadrapassel:3.11.1:
apps:rygel:0.21.0:
apps:seahorse:3.10.1:
apps:swell-foop:3.11.1:
apps:tali:3.11.1:
apps:vinagre:3.10.1:

[mrpdaemon]

Maybe we can put the ebuilds into the tree hardmasked with empty KEYWORDS? And maintain package.unmask/package.keywords/package.use files for 3.11 specifically?

[cnd]

@mrpdaemon

I can see the reason for it when bumping packages will possibly cause some problems for ourselves. But for now I can't see the reason to maintain package.unmask/package.keywords file for working ebuilds. What is the profit?

[mrpdaemon]

So it depends on whether we want to have both GNOME 3.10.x (stable) and 3.11.x (development) versions available through the same overlay. If we have ebuilds for both of those versions in the same overlay then we should provide users with a way to choose which one they would like to use. Right now all 3.10.x stuff is marked ~arch, and we have plenty of users of the overlay, so I believe we can keep ~arch for 3.10.x and use empty keywords for 3.11.x. Since it would be quite a hassle to manually unmask all components needed for 3.11.x, it would be convenient to users if we provided a specific package.unmask and package.keywords file for easy unmasking of 3.11.x.

[cnd]

@mrpdaemon well I'm fine with it.

[ibqn]

Do we want to place all 3.11.x related ebuild in another overlay or in another branch at least, so this 3.10.x related work can be easier continued and merged to portage some day? I am for separation :-)

[mrpdaemon]

I'm fine either way. I think the advantage of having them in the same branch/repo would be that whenever we do a fix to the 3.10.x ebuilds we would also apply the change to the 3.11.x ebuild whenever appropriate. If 3.11.x is on another branch or another repository I think this is less likely to happen.

[cnd]

@ibqn @mrpdaemon master branch always should contain top working versions. I'm fine with creating 3.10 branch if someone will maintain it but he should synchronize all the changes with master branch then because I don't want to remove previous (3.10) version from master.

[lxnay]

Please take into consideration that there are people using this overlay just to get GNOME 3.10 stable. Just try not to make their life harder ;-)

[cnd]

@lxnay we will try to keep last stable and unstable versions available. But 3.10.1 was bumped or will be to 3.10.2

[mrpdaemon]

@Heather at least until GNOME 3.10 is in portage it would make sense to keep this overlay follow 3.10.x on ~arch. I don't see any downsides to hard masking 3.11.x stuff, especially with proper profile files to easily mass-unmask stuff.

I'd say the natural time to switch 3.11.x into ~arch would be around 3.11.90 or equivalent, where it's more of a release candidate than a development snapshot.

[cnd]

@mrpdaemon well for now probably 3.11.x versions release in the same time as 3.10.x+1 . If we follow upstream then they call 3.10 stable and 3.11 unstable. So I see ideal situation when 3.10 will have stable keywords and 3.11 unstable.

But sure we can't follow it with many reasons but at least because we can't call our 3.10 really stable for now and also it's overlay so it should not provide stable ebuilds.

By the way with masking we should create this mask files templates so we can point team to keep keywords for 3.11 there + add it to readme + maybe to news (iirc it's possible).

[TaraRed]

We should just create a mask file than to create synced branches which introduce the possibility for errors; and besides that, you add a mask once as opposed to having to sync every time so it spares out some work too. Not much people need 3.11 anyway; so, it should effectively be a win-win situation to just mask it.