Thanks Valentyn, I can reproduce the large icon problem too by setting com.canonical.Unity.Panel systray-whitelist to 'all'.
Working on this and the language problem now.

Valentyn wrote:

I would like you to add compiz-plugins-extra by default or like an extra ebuild to overlay. Ebuilds from main tree are not working because of version conflict.

What ebuilds are causing the conflict ?
I can try and make it as compatible as possible but compiz-plugins-extra was absorbed into compiz around version 0.9.8.
Also, the compiz we use is now being developed by Canonical after it seems Compiz upstream has paused or died since August 2011 at version 0.9.5.92.1 ( Gentoo's version even older at 0.8.8 ), see https://launchpad.net/compiz vs. http://releases.compiz.org/
So even if we resolve the version conflict it could well not work anyway because it's relying on such an old version of compiz.

@renegart
I've added unity-base/ido to net-im/empathy's DEPEND list.

The case of the disappearing tarballs happens when using the developmental release.
As Canonical develop and update packages in the developmental release, they delete the old tarball.
So for everyone's sanity I'm trying to keep everything at Quantal until Raring is released, then switch over to Raring.

There are some exceptions to bumping up to Raring though when there are critical bugs (the Quantal release of gtk+:3 segfaulting when using Adwaita theme is one).
Flowing on from that I've bumped all the gnome 99.3.6 packages into Raring versions so that the versions in our small subset of gnome packages closely match their respective dependency versions that are already in the portage tree.

But everything else will remain at Quantal versions as much as possible until Raring is released.

@sormy

sormy wrote:

I'm installing new clean system with stable gentoo overlay and current-state unity-gentoo overlay:

I can't reproduce this without maybe installing Gentoo in a VM using the new install method.

sormy wrote:

Suggestions:
1) May be it's better to mask gentoo-overlay packages instead of 99-prefixing, for example, like package.mask:

Code:

dev-libs/glib::gentoo

Great idea!
The version prefixing is something I've never been comfortable with but saw it as a necessary beast to keep the integrity of the user's system and that of the overlay.
The user would have to implement a symlink from a package.mask file maintained in the overlay, into their own /etc/portage/package.mask/ directory as package.mask is not respected directly from overlays.

sormy wrote:

2) May be it's better to switch all overlay packages to ~arch branch like (with single line without per package keyword line):

Code:

*/*::unity-gentoo

Also another great suggestion to have this replace the current symlink of /var/lib/layman/unity-gentoo/PACKAGES into /etc/portage/package.keywords/

What ebuilds are causing the conflict ?
I can try and make it as compatible as possible but compiz-plugins-extra was absorbed into compiz around version 0.9.8.
Also, the compiz we use is now being developed by Canonical after it seems Compiz upstream has paused or died since August 2011 at version 0.9.5.92.1 ( Gentoo's version even older at 0.8.8 ), see https://launchpad.net/compiz vs. http://releases.compiz.org/
So even if we resolve the version conflict it could well not work anyway because it's relying on such an old version of compiz.

But do Canonical have their own compiz-plugins-extra? (yes, they do 'cause it's possible to install that package in Ubuntu). As I know ccsm, main-plugins etc are in general ebuild.
So I just ask you to add extra-plugins for compiz. I will be very grateful to you.

small other question...
I've set up a new system with Unity. At my old system (which where initially running with Ubunutu )Thunderbird and Banshee are added to the systray menus ('letter' and 'audio' - icons).
On the new system that doesn't happens. Is there an option, which I've to set to add the programs?

But do Canonical have their own compiz-plugins-extra? (yes, they do 'cause it's possible to install that package in Ubuntu). As I know ccsm, main-plugins etc are in general ebuild.
So I just ask you to add extra-plugins for compiz. I will be very grateful to you.

We could also have a compiz-plugins-extra package that provides nothing more than a Copyright and Changelog file, but why ?
Why are we needing to provide a compiz-plugins-extra package at all ?
What is needing it, or are you thinking that it somehow provides some extra compiz plugins ?

small other question...
I've set up a new system with Unity. At my old system (which where initially running with Ubunutu )Thunderbird and Banshee are added to the systray menus ('letter' and 'audio' - icons).
On the new system that doesn't happens. Is there an option, which I've to set to add the programs?

Not sure (yet) as I use Evolution and Rhythmbox.
Evolution doesn't integrate to the messages indicator yet afaik, but Banshee I would have thought should have appeared in the sound indicator menu.

You could take a look at the 'interested-media-players' and 'preferred-media-players' settings in dconf-editor's com.canonical.indicator.sound schema for adding Banshee.
And the 'applications' setting in dconf-editor's com.canonical.indicator.messages schema for adding Thunderbird, though I think this will just provide a means to launch Thunderbird from the message indicator.
For Thunderbird messages indicator integration notification of incoming and unread messages, this may require a small patch for Thunderbird.

You could take a look at the 'interested-media-players' and 'preferred-media-players' settings in dconf-editor's com.canonical.indicator.sound schema for adding Banshee.
And the 'applications' setting in dconf-editor's com.canonical.indicator.messages schema for adding Thunderbird, though I think this will just provide a means to launch Thunderbird from the message indicator.
For Thunderbird messages indicator integration notification of incoming and unread messages, this may require a small patch for Thunderbird.

Your tip was correct. I've compared the setting of my old system with the new one. Thunderbird.desktop need to be added to the message-indicator.
Thx

The 99. prefixing has now been removed and we rely on masking the packages from ::gentoo repo using sormy's solution (thanks sormy).

This requires some additional package.mask and package.keywords setup but should be a once off set and forget.
The overlay now requires symlinking the file 'unity-portage.pmask' to '/etc/portage/package.mask/unity-portage.pmask'

All packages are keyword masked and require keyword unmasking by adding '*/*::unity-gentoo' to your package.keywords file.
You can safely remove the old /etc/portage/package.keywords/unity-gentoo symlink that points to /var/lib/layman/unity-gentoo/PACKAGES

package.unmask files override package.mask files, so be sure that none of the packages listed in 'unity-portage.pmask' already lie in your /etc/portage/package.unmask file, or if they do that they unmask in a repo specific way.
eg. www-client/chromium::unity-gentoo

There is a new eclass ubuntu-versionator.eclass.
It checks for the correct masking setup (package.mask and keyword.mask) needed for the overlay to integrate with the main portage tree.

The eclass also uses the new ebuild naming scheme to generate a valid UVER string that is used in SRC_URI.
This has the following benefits:
* Removes code duplication
* Easier patchset version bumping (ebuild now just needs to be renamed and digested, instead of the old way of open ebuild, edit ebuild, save ebuild, digest ebuild)
* Minor patchset bumps are picked up by emerge as upgrades (eg. gtk+-3.6.4's 0ubuntu5 patchset tarball is bumped up to 0ubuntu6).

Every ebuild has now been renamed to this new naming scheme.
The version_check.sh script in the top level directory has been re-worked to use the new naming scheme.

It's been thoroughly tested so all should be OK, but if you're already using the overlay you may need to do the following to ensure all packages are installed at once to upgrade/downgrade to the new ebuild naming scheme:

Code:

emerge -1a `eix -I --in-overlay unity-gentoo --only-names`

Last edited by shiznix on Fri Feb 08, 2013 8:50 am; edited 1 time in total

I see we have new naming scheme =) And world need to be reemerged now =)
Didn't test yet. But in previous overlay there are soem problems:
1) deja-dup depend on gnome-control-center but ebuild didn't know about that
2) a lot of packages from main gentoo repo need to be keyworded to build unity (i can post my files for keywords and use flags)
3) Zeitgeist have circular dependencies with unity-related use flags. So i emerge just zeitgest with default flags and after that i can emerge unity-meta.
4) Portage sometimes die when trying to resolve conflicts with emerging unity-meta (problem described above), fixed with:

I see we have new naming scheme =) And world need to be reemerged now =)
Didn't test yet. But in previous overlay there are soem problems:
1) deja-dup depend on gnome-control-center but ebuild didn't know about that
2) a lot of packages from main gentoo repo need to be keyworded to build unity (i can post my files for keywords and use flags)
3) Zeitgeist have circular dependencies with unity-related use flags. So i emerge just zeitgest with default flags and after that i can emerge unity-meta.
4) Portage sometimes die when trying to resolve conflicts with emerging unity-meta (problem described above), fixed with:

1) Fixed, thanks for reporting.
2) Impossible to maintain keyword states for packages outside the overlay.
3) Due to main portage tree ebuilds for zeitgeist[fts] and zeitgeist-extensions[fts] being mutually exclusive and Unity requires both zeitgeist and zeitgeist-extensions be installed (for geolocation).
Portage tree enables +fts by default for zeitgeist, so we go with that.
4) Not sure on this one, a bug in portage perhaps ?
I can't see anything out of the ordinary in unity-meta ebuild that could trigger it, but unity-meta ebuild internals have changed recently (99. prefix and unity2d blocker removal) so I'd be interested if you can reproduce this again with latest overlay sync update and without the slot_collision.py edit.
If it still causes a problem then a bug should be filed on bugs.gentoo.org.

The following keyword changes are necessary to proceed:
#required by gnome-base/gnome-fallback-3.6.2, required by gnome-base/gnome-3.6.2[fallback], required by @selecte$
=x11-wm/metacity-2.34.13 ~amd64

You forgot to unmask gentoo-unity overlay packages according to documentation. Read last post from shiznix.

Nope, the checks done by the unity-packages succeeding. Also some of the mentioned packages are masked by the overlay but didn't provided as replacement by the overlay.

It's because version bumps needed to happen to the previously 99. prefixed packages, they now need to be in step with main tree version dependencies.

So am bumping the following to Raring:
x11-wm/metacity to 2.34.13
gnome-extra/nm-applet to 0.9.7.995 (This requires networkmanager-0.9.7 as Gentoo's gnome-core-apps-3.6.2[networkmanager] requires >=nm-applet-0.9.6.4, but Ubuntu jump straight from -0.9.6.2 to -0.9.7)
net-im/empathy to 3.6.3

You forgot to unmask gentoo-unity overlay packages according to documentation. Read last post from shiznix.

Nope, the checks done by the unity-packages succeeding. Also some of the mentioned packages are masked by the overlay but didn't provided as replacement by the overlay.

It's because version bumps needed to happen to the previously 99. prefixed packages, they now need to be in step with main tree version dependencies.

So am bumping the following to Raring:
x11-wm/metacity to 2.34.13
gnome-extra/nm-applet to 0.9.7.995 (This requires networkmanager-0.9.7 as Gentoo's gnome-core-apps-3.6.2[networkmanager] requires >=nm-applet-0.9.6.4, but Ubuntu jump straight from -0.9.6.2 to -0.9.7)
net-im/empathy to 3.6.3

Yesterday evening my problem was that your mask-file masked the mentioned packages but your overlay didn't provided replacements. In meantime it seems you comitted the missing files and now it works.

So I was looking at trying to fix the large systray icons bug that can happen when setting com.canonical.Unity.Panel systray-whitelist to 'all', when I found that Canonical have removed the systray whitelist feature completely in new versions of Unity.

They now expect every GUI application developer to port their software to use Ubuntu's own appindicator API, and if they don't then their application will not show in Unity's panel.

It seems like my default /etc/init.d/xdm with "gdm" in /etc/conf.d/xdm and XSESSION="unity" start every time "gnome3" instead of "unity".
startx works fine and run unity. Do you have any suggestions or workarounds?