Bugzilla Bug 215337

2008-02-21
Alexandria 0.6.3 released
With new iPod Notes export, and a new Amazon ECS 4.0 provider, as well as
greater stability.

Created an attachment (id=147708) [details]
Ebuild for alexandria 0.6.3

Created an attachment (id=147710) [details]
Patch to fix potential segfault

Patch that disables tooltips on icon view. I get a segmentation fault in the
mouse motion handler. This seems to be a bug in ruby-gtk2, but I haven't had
time to dig into it further, other than confirming that it segfaults on two
separate Gentoo amd64 systems, but not on an Ubuntu box.

Sorry I haven't filed an ebuild for this sooner, but I've been wanting to find
the cause of the segfault.

I've filed separate bugs (with ebuilds) for a couple of optional dependencies
in bugs #215457 and #215458. If you don't think these should be added to the
tree then alexandria remains usable without them.

The bug causing the segfault seems to be in the get_path method of GtkIconView,
but I've had the same results trying get_item as well.

Might be a good idea to open a separate bug for the ruby-gtk2 bug so we can
track that. Might be nice to test it on a x86 system as well, I'm not sure
Ubuntu is amd64?

We've just added a new mirror for rubyforge stuff, so that you won't need the
download id anymore:

SRC_URI="mirror://rubyforge/${PN}/${P}.tar.gz"

It makes sense to me to add the other ruby stuff as well, but I'm not sure
about the use flags. In any case it would be good to also get descriptions for
them. Have a look at profiles/use.local.desc to see what needs to be provided
in the end.

I would rather see use flags describing what people will get, rather then the
underlying package. amazon makes sense to me, I guess zoom makes sense as well
given that it is for the Z39.50 Object-Orientation Model. :-)

For mechanize it may make sense to call the use flag for the site it will
scrape? evo is already used in the context of evolution (mail client) support,
so perhaps another name might be better, and imagesize also sounds like it may
need a better more descriptive name.

Another approach for this (e.g. taken by git) is to list the extra packages
that can unlock additional functionality. See git's pkt_postinst().

It would be great if you could have another look at these, while I go and have
a look at the dependencies.

...and so I go and check out what dev-ruby/revolution is about... forget my
remarks about the evo use flag. :-)

I've filed a separate bug #215634 for the GtkIconView issue, with a patch
attached which fixes it for me.

$ alexandria
Can't load hpricot, hence provider Amazon not available

dev-ruby/hpricot is run-time dependency for Amazon functionality.

Well, you can read INSTALL for more accurate notes. There are various missing
dependencies, and also, most of the listed ones are not build-time dependencies
and shouldn't be included in DEPEND. I'll be posted an updated ebuild proposal.

Although, we should decide something...

Do we really want to pull in optional run-time dependencies through USE flags?
Maybe we can drop most of them and give some advice in pkg_postinst, and for
some of them we could just force them (if they're little enough).

Created an attachment (id=147926) [details]
Updated ebuild

An updated version of my ebuild. I've switched to the rubyforge mirror, listed
the dependencies better (I think - could someone check this please?) and added
hpricot as a dependency for amazon - I had read it was needed for mechanize but
the INSTALL file doesn't make it clear that it's also needed for amazon)

I've also decided to force imagesize as a dependency as the functionality is
probably going to be used by most people. I think revolution should remain as a
use flag as people using evolution will expect the evo useflag to enable
evolution support in all packages that can support it. On the data providers I
think the post install message might be the most sensible thing to do but would
like to know what others think.

Is there a way to patch the default position of the old (v3) amazon provider to
the bottom of the list, since Amazon stopped v3 access?

Created an attachment (id=149224) [details]
Patch to remove Amazon AWS 3.x provider

This patch completely disables the Amazon AWS 3.x provider. Moving it to the
bottom of the list is just a workaround and if we're patching the code we might
as well remove it completely.

Created an attachment (id=149226) [details]
Updated ebuild

Updated ebuild which includes the above patch and also adds a log message to
inform people about what dependencies they need for the different book
providers while removing the use flags for those.

No more blockers! \o/

coldwind, can this be pushed to tree now? :D

I've just added the latest version of the 0.6.3 ebuild and the amazon patch to
CVS. John, thanks for providing a couple of revisions for the ebuild, and
thanks to the others for feedback and testing.

Thanks for the work John :D