Re: [RFC] GTK+ theme naming
On Tue, Dec 11, 2001 at 05:23:52PM +0100, Filip Van Raemdonck <firstname.lastname@example.org> was heard to say:
> Thus my question: why are all these packages called gtk-engines-foo?
> For Eds packages, it makes sense, although it would probably be more correct
> to call them gtk-engine-foo as each of them contains only one theme engine;
> but for the others there's no valid reason at all.
Yes there is; they're all GTK+ theme engines, and the intent is to
indicate that in the package name. (it's arguable that there are better
names, but that's why they're all the same)
The themes from the GTK+ source were, for obvious reasons, the first
ones, and everyone else independently modeled their names and
descriptions after those.
It's the same reason that all the Python modules are called python-x.
If you want to rename them all to gtk-theme-foo or something, I would
go along with it, but with the freeze coming soon, you'd have to do a
lot of convincing of other people. Especially since the gtk-engine-*
convention was established some time ago, and we'd need to make sure
that people upgrading from stable don't lose their theme engines.
(read: Lots Of Dummy Packages)
/-------------------- Daniel Burrows <email@example.com> -------------------\
| Exhilaration is that feeling you get just |
| after a great idea hits you, and just before |
| you realize what is wrong with it. |
\------- (if (not (understand-this)) (go-to http://www.schemers.org)) --------/