Bugzilla Bug 207396

I cooked up an ebuild for gnome-do and wanted to share it. Maybe someone could
add it to the tree. I'm also willing to add ebuilds for future releases here.
See http://do.davebsd.com/.

Martin


Reproducible: Always

Steps to Reproduce:
1.emerge gnome-do
2.
3.

Actual Results:  
Not found

Expected Results:  
[ebuild  N   ] app-misc/gnome-do-0.3.0.1

Created an attachment (id=141772) [details]
The ebuild

unfortunately, these kind of application don't seem to survive that much after
the initial buzz. I think I had to fix one or two things to make it work
properly so I'll try to post here the fixes on monday.

graaff has an ebuild in his overlay and there were considerations of him adding
it to portage when some quirks with plugins (or some such) are worked out.
CC'ing him

My current ebuild seems to work fine on the two machines I've played around
with. It currently does trigger a bug in the new compositor code in metacity,
though, so I'm kinda waiting for that to be fixed so that I can test that.

Regarding the plugins: currently these are distributed as binary dlls to be put
in your home directory somewhere. It would be nice if we could support at least
a few of those as source builds (from upstream SVN). My thinking was to add
some USE flags for common plugins like rhythmbox or evolution.

I agree also with Gilles' sentiment and would like to see how things progress,
especially regarding releases.

(In reply to comment #4)
> My current ebuild seems to work fine on the two machines I've played around
> with. It currently does trigger a bug in the new compositor code in metacity,
> though, so I'm kinda waiting for that to be fixed so that I can test that.

Works fine for me.

> Regarding the plugins: currently these are distributed as binary dlls to be put
> in your home directory somewhere. It would be nice if we could support at least
> a few of those as source builds (from upstream SVN). My thinking was to add

You can pull in a set of plugins from the site (source not binaries). I've
written up an ebuild for this. Will attach.

Thanks!

Created an attachment (id=144322) [details]
plugins ebuild

Arun, thanks for the plugins ebuild, it works fine. I guess it would be nice if
it had USE flags for the different packages, so that only relevant plugins
would be built. That would also make the evolution-sharp dependency
conditional. Could you have a look at this?

@gnome: I would be happy to be the maintainer for this. Can I put gnome as the
backup herd?

no strong objection from me. There are not much people in gnome herd that also
do mono stuff so I'm not sure what others would say.

(In reply to comment #7)
> Arun, thanks for the plugins ebuild, it works fine. I guess it would be nice if
> it had USE flags for the different packages, so that only relevant plugins
> would be built. That would also make the evolution-sharp dependency
> conditional. Could you have a look at this?

The plugins package actually only checks for evo-sharp at compile time (the
remaining are runtime dependencies).

I've written a small patch to allow enabling/disabling the evo plugin check
(and submitted upstream -- https://bugs.launchpad.net/gc/+bug/195678), and the
corresponding USE flag is in the updated ebuild. When I get some more time,
I'll try to add --enable flags for the rest of the plugins too and submit
upstream.

Let me know if you'd like any further changes.

Thanks!

Created an attachment (id=144656) [details]
Patch to make the Evolution plugin optional

Created an attachment (id=144657) [details]
Update plugins ebuild with "evo" USE flag

Created an attachment (id=144727) [details]
Make more plugins depend on USE flags

Based on feedback from the Do devs, I've made a few more plugins optional (this
was not done for all plugins because that causes bloat)

Created an attachment (id=144728) [details]
gnome-do-plugins ebuild with "evo" and "amarok" USE flags

Add "evo" and "amarok" USE flags to the ebuild

Looks like the actual upstream bug report link is
https://bugs.launchpad.net/do/+bug/195678

(In reply to comment #14)
> Looks like the actual upstream bug report link is
> https://bugs.launchpad.net/do/+bug/195678

Phew, they finally changed the project name on Launchpad, I guess. Are there
any other changes required in the ebuild?

No, the plugins ebuild looks fine to me. Now I just need to find a bit of time
to land everything correctly in Gentoo's CVS. Hopefully this week...

gnome-do and gnome-do-plugins are now in Gentoo CVS. Thanks everyone for the
contributions!

latest do-plugins ebuild is for 0.4.0 while newest one is 0.6.1, can someone
make an ebuild for it?

Also, the latest Gnome-do is 0.5.97, whereas the latest available in portage is 
0.4.2.0-r1. A more recent ebuild for both would be very much appreciated.

(In reply to comment #19)
> Also, the latest Gnome-do is 0.5.97, whereas the latest available in portage is 
> 0.4.2.0-r1. A more recent ebuild for both would be very much appreciated.
> 

Correction, 0.5.99, which I assume is to be one of the last testing phases
before the release of 0.6.

I'm having a look at the 0.4.2.0-r1 ebuild to see if I can update it for more
recent versions, but this is my first attempt at anything ebuild related, so
I'm unsure how I'll go.

Mieszko, Jason, please don't add unrelated comments to already closed bugs.
Instead search for an open bug or add a new bug. Hint: see bug #225911.