Added more themes. Pretty straightforward. BTW, I've noticed that apparently there's no similar package for GTK themes (there's the thinice engine, though). I'm thinking about writing en ebuild for GTK themes... Is it a good idea? Maybe themes alone shouldn't have their own ebuild? Any comments? Thanks, Leonardo
Created attachment 609 [details] sawfish-themes-0.0.1-r2.ebuild
Leonardo, Have a look at bug #1294 -- it talks about the gtk-themes ebuild in x11-libs. That ebuild has been masked, because the SRC_URI was wrong in it. I haven't had much opportunity to mess with it yet, but if you'd like to propose something for an alternate way of getting the themes, I'm all ears.
I'll take a look at the old-gtk-themes ebuild then. Maybe we can use classic.themes.org URIs here too? If you're ok with it, I will give it a try and let you know if I end up with something useful.
I am absolutely fine with it. I haven't had much time to look through that ebuild, so it has sadly gotten a fairly low priority on my TODO list. If you're willing and able, I am more than happy :)
Leonardo, It would be preferrable to have the themes/engines all bundled in one ebuild, apparently. Most users would rather install all of them to try. For those worried about bloat, they can manually remove the themes that they do not want/need.
<leonardop> Now, the thing is that my gtk-themes package depends on every gtk-engines-* package, because: <seemant> actually, I have a question for you <leonardop> (a) Some themes requires some of the engines <seemant> what exactly is an engine vs. a theme? <leonardop> (b) In fact, every gtk engine comes with a sample theme, so they should get included <leonardop> An engine is basically a library that is implemented directly by GTK+ <leonardop> engines need to compile stuff and installs it under.... <leonardop> wait a sec. <seemant> k <leonardop> /usr/lib/gtk/themes/engines <leonardop> themes are just plain text files that describe a "display" <seemant> so can we consider a theme (in gentoo package terms) to be an engine <seemant> er <leonardop> Most of the normal themes require the `pixmap' engine <seemant> so can we consider a theme (in gentoo package terms) to be an engine + textfile to describe "display" ? <leonardop> in gentoo package terms, I think there should be a number of engines, and one ebuild for lots of regular themes <leonardop> But you see, the gtk-themes package depends on every engine, so, you may only merge gtk-themes, and everything is there for you <seemant> can you show me many themes per engine?<seemant> basically, what does it buy us to have separate ebuilds for each engine? <seemant> and please remember you're talking to a person with no knowledge of themes other than firing up "switch" to change the GTK theme <seemant> :P <leonardop> Oh, well, it's just more flexible, IMO <leonardop> well... Let's say you know you just want a particular theme that you saw the other day... let's call it CoolGtkTheme <leonardop> CoolGtkTheme may depend on one or more engines... usually you can find that info reading the README or something <leonardop> most of the GTK+ themes depend on the `pixmap' engine, because that's the engine which (no surprise here), allows to import images inside themes <leonardop> so, let us say that CoolGtkTheme depends on the `pixmap' engine. You may then just install the gtk-engine(s?)-pixmap package <leonardop> and then CoolGtkTheme from my-favorite-eye-candy-website.org <leonardop> I agree in that most users just want all the themes, so they don't even have to know about engines and other boring matters <leonardop> the gtk-themes package should take care of everything via DEPENDS <leonardop> I don't know, maybe it's not a big deal, and it would be easier to just bundle all that stuff in just one ebuild <leonardop> But, the fact is that every engine is actually a separate library, and I think Portage should reflect that.
Leonardo, As for eclasses, this is a good guide: http://gentoo.org/doc/eclass-howto.html
*** Bug 1294 has been marked as a duplicate of this bug. ***
Leonardo, I tried to add this to portage, but it looks like the SRC_URI's need to be updated since freshmeat.net ate themes.org.
Created attachment 1173 [details] sawfish-themes-0.0.1-r2.ebuild SRC_URI updated. Thanks for the notice.
Leonardo, I've added this to portage. One more thing -- there's a sawfish-2.0 in portage. Will these themes work with that? If not, can you package up a new ebuild for it, please? I won't take so long this time. There is now an x11-themes category, as you can see :)
