'album' is way more fun if you don't have to download and install themes, plugins and language options (IOW: everything contained in <http://marginalhacks.com/bin/album_data.tar.gz>) by yourself. IMHO this can be done as well by the ebuild. Maybe a new USE-flag can be introduced to decide whether to install themes etc. in /usr/share/album. Maybe /usr/share/album should be created by the ebuild anyway so there is a well-defined place where that optional stuff can go.
Sorry, won't be done at least until upstream provides versioned tarballs for themes etc; it's disallowed by our policy for very good reason (perpetually broken checksums and digest collisions). And no, we certainly won't be mirroring them manually. :)
(In reply to comment #1) > Sorry, won't be done at least until upstream provides versioned tarballs for > themes etc; it's disallowed by our policy for very good reason (perpetually > broken checksums and digest collisions). And no, we certainly won't be > mirroring them manually. :) Hum...too bad. I'm not sure if themes etc. change as often as the actual program. Maybe then this should go into a separate package (of course, *if* there are versioned tarballs someday)... But what about at least having the ebuild create a /usr/share/album dir? Do I have to file a new bug for that? Or can we just reopen this one? It seems to be a trivial change to the ebuild which even I could do. ;-)
(In reply to comment #2) > Hum...too bad. I'm not sure if themes etc. change as often as the actual > program. Maybe then this should go into a separate package Sorry, we've done this mistake once w/ drupal, and won't ever do it again (see Bug 89125 for the fun). And it wasn't even unversioned there, they just kept changing the tarballs without any version bump.
