Debian Bug report logs -
#123456
ITP: eazel-engine -- Crux theme for GTK+
Reported by: Filip Van Raemdonck <mechanix@debian.org>
Date: Tue, 11 Dec 2001 17:33:03 UTC
Severity: wishlist
Fixed in version eazel-engine/0.3-1
Done: Filip Van Raemdonck <mechanix@debian.org>
Bug is archived. No further changes may be made.
Toggle useless messages
Report forwarded to debian-bugs-dist@lists.debian.org, debian-devel@lists.debian.org, wnpp@debian.org:
Bug#123456; Package wnpp.
(full text, mbox, link).
Acknowledgement sent to Filip Van Raemdonck <mechanix@debian.org>:
New Bug report received and forwarded. Copy sent to debian-devel@lists.debian.org, wnpp@debian.org.
(full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Package: wnpp
Version: N/A; reported 2001-12-11
Severity: wishlist
* Package name : eazel-engine
Version : 0.3
* URL : http://gtk.classic.themes.org/
* License : GPL
Description : Crux theme for GTK+
This is the upstream (and source) package name, binary will most likely be
gtk-theme-crux.
Package: gtk-theme-crux
Architecture: any
Depends: ${shlibs:Depends}
Description: Crux theme for GTK+
This package contains the Crux theme for GTK+, also know as the Eazel
engine.
.
Themes modify the way GTK-using programs look. The programs do not need
to be modified to use themes; the support is built in to GTK+.
-- System Information
Debian Release: sid
Architecture: i386
Kernel: Linux lucretia 2.4.15-ifix #4 Wed Nov 28 09:19:16 UTC 2001 i686
Locale: LANG=C, LC_CTYPE=nl_BE@euro
--
Buyer's Guide for a Operating System:
Don't care to know: Mac
Don't mind knowing but not too much: Windows
Hit me! I can take it!: Linux
-- Stephen Torri
Information forwarded to debian-bugs-dist@lists.debian.org, wnpp@debian.org:
Bug#123456; Package wnpp.
(full text, mbox, link).
Acknowledgement sent to Erich Schubert <erich.schubert@mucl.de>:
Extra info received and forwarded to list. Copy sent to wnpp@debian.org.
(full text, mbox, link).
Message #10 received at 123456@bugs.debian.org (full text, mbox, reply):
> * Package name : eazel-engine
>
> This is the upstream (and source) package name, binary will most likely be
> gtk-theme-crux.
This actually is a real engine, not just a theme, so i'd prefer the name
gtk-engines-eazel or gtk-engines-crux
Theme packages can easily be created with a special package (sorry,
don't know the name right now, theme-converters or something like that)
The Engines do contain real binary code afaik; so it's useful to have
them as packages.
Ordinary Themes just use one of the default engines and modify options
and graphics, they can easily be installed by the users themselves;
So i do like the idea of doing "apt-get install gtk-engines-*" to
install all available gtk engines; so people actually can use any theme
they want and install it themselves by extracting a tgz file; so they
don't need to compile anything.
So i'd suggest using gtk-engines-* for any gtk theme containing real
binary libraries; maybe gtk-theme-* for config file based themes only.
Maybe i'm wrong and eazel-engine does not require compilation?
Greetings,
Erich
Information forwarded to debian-bugs-dist@lists.debian.org, wnpp@debian.org:
Bug#123456; Package wnpp.
(full text, mbox, link).
Acknowledgement sent to Junichi Uekawa <dancer@netfort.gr.jp>:
Extra info received and forwarded to list. Copy sent to wnpp@debian.org.
(full text, mbox, link).
Message #15 received at 123456@bugs.debian.org (full text, mbox, reply):
On Tue, 11 Dec 2001 18:29:22 +0100
Filip Van Raemdonck <mechanix@debian.org> wrote:
> This is the upstream (and source) package name, binary will most likely be
> gtk-theme-crux.
why not gtk-engines-crux?
regards,
junichi
--
dancer@debian.org http://www.netfort.gr.jp/~dancer
Information forwarded to debian-bugs-dist@lists.debian.org, wnpp@debian.org:
Bug#123456; Package wnpp.
(full text, mbox, link).
Acknowledgement sent to Filip Van Raemdonck <mechanix@debian.org>:
Extra info received and forwarded to list. Copy sent to wnpp@debian.org.
(full text, mbox, link).
Message #20 received at 123456@bugs.debian.org (full text, mbox, reply):
On Wed, 12 Dec 2001 12:50:34 +0900, Junichi Uekawa wrote:
>
> On Tue, 11 Dec 2001 18:29:22 +0100, Filip Van Raemdonck wrote:
> > This is the upstream (and source) package name, binary will most likely be
> > gtk-theme-crux.
>
> why not gtk-engines-crux?
On Tue, Dec 11, 2001 at 10:36:28PM +0100, Erich Schubert wrote:
> > * Package name : eazel-engine
> >
> > This is the upstream (and source) package name, binary will most likely be
> > gtk-theme-crux.
>
> This actually is a real engine, not just a theme, so i'd prefer the name
> gtk-engines-eazel or gtk-engines-crux
About these names: check the thread on debian-devel a couple of messages
before my ITP (subject: [RFC] GTK+ theme naming).
Daniel Burrows (who has packaged a couple of other themes) seemed to agree
that gtk-engines-* is probably (most likely) not the best name for these
packages.
> Theme packages can easily be created with a special package (sorry,
> don't know the name right now, theme-converters or something like that)
>
> The Engines do contain real binary code afaik; so it's useful to have
> them as packages.
> Ordinary Themes just use one of the default engines and modify options
> and graphics, they can easily be installed by the users themselves;
>
> So i do like the idea of doing "apt-get install gtk-engines-*" to
> install all available gtk engines; so people actually can use any theme
> they want and install it themselves by extracting a tgz file; so they
> don't need to compile anything.
>
> So i'd suggest using gtk-engines-* for any gtk theme containing real
> binary libraries; maybe gtk-theme-* for config file based themes only.
>
> Maybe i'm wrong and eazel-engine does not require compilation?
No, you're correct - it does require compilation.
Hmmm... maybe it would be useful to put the actual engine and theme in a
separate package. (and that would probably make most sense, wrt. naming of
the various binary packages too)
The only downside of this is "package bloat" (more and smaller packages).
I'll propose this on the thread I started.
Regards,
Filip
--
The New Testament offers the basis for modern computer coding theory, in the
form of an affirmation of the binary number system:
"But let your communication be Yea, yea; nay, nay: for whatsoever is more
than these cometh of evil." (Matthew 5:37)
-- Daniel Burrows
Information forwarded to debian-bugs-dist@lists.debian.org, wnpp@debian.org:
Bug#123456; Package wnpp.
(full text, mbox, link).
Acknowledgement sent to Daniel Burrows <dburrows@debian.org>:
Extra info received and forwarded to list. Copy sent to wnpp@debian.org.
(full text, mbox, link).
Message #25 received at 123456@bugs.debian.org (full text, mbox, reply):
On Wed, Dec 12, 2001 at 10:43:13AM +0100, Filip Van Raemdonck <mechanix@debian.org> was heard to say:
> On Tue, Dec 11, 2001 at 10:36:28PM +0100, Erich Schubert wrote:
> > > * Package name : eazel-engine
> > >
> > > This is the upstream (and source) package name, binary will most likely be
> > > gtk-theme-crux.
> >
> > This actually is a real engine, not just a theme, so i'd prefer the name
> > gtk-engines-eazel or gtk-engines-crux
>
> About these names: check the thread on debian-devel a couple of messages
> before my ITP (subject: [RFC] GTK+ theme naming).
> Daniel Burrows (who has packaged a couple of other themes) seemed to agree
> that gtk-engines-* is probably (most likely) not the best name for these
> packages.
It may not be the best one, but I think that we should be consistent
now that we have a convention. We can worry about moving to a better
naming scheme in the future.
> No, you're correct - it does require compilation.
> Hmmm... maybe it would be useful to put the actual engine and theme in a
> separate package. (and that would probably make most sense, wrt. naming of
> the various binary packages too)
I don't see any benefit from this.
Daniel
--
/-------------------- Daniel Burrows <dburrows@debian.org> -------------------\
| Put no trust in cryptic comments. |
\-Evil Overlord, Inc: planning your future today. http://www.eviloverlord.com-/
Reply sent to Filip Van Raemdonck <mechanix@debian.org>:
You have taken responsibility.
(full text, mbox, link).
Notification sent to Filip Van Raemdonck <mechanix@debian.org>:
Bug acknowledged by developer.
(full text, mbox, link).
Message #30 received at 123456-close@bugs.debian.org (full text, mbox, reply):
We believe that the bug you reported is fixed in the latest version of
eazel-engine, which has been installed in the Debian FTP archive:
eazel-engine_0.3-1.diff.gz
to pool/main/e/eazel-engine/eazel-engine_0.3-1.diff.gz
eazel-engine_0.3-1.dsc
to pool/main/e/eazel-engine/eazel-engine_0.3-1.dsc
eazel-engine_0.3.orig.tar.gz
to pool/main/e/eazel-engine/eazel-engine_0.3.orig.tar.gz
gtk-engines-eazel_0.3-1_i386.deb
to pool/main/e/eazel-engine/gtk-engines-eazel_0.3-1_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 123456@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Filip Van Raemdonck <mechanix@debian.org> (supplier of updated eazel-engine package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 11 Dec 2001 19:37:50 +0100
Source: eazel-engine
Binary: gtk-engines-eazel
Architecture: source i386
Version: 0.3-1
Distribution: unstable
Urgency: low
Maintainer: Filip Van Raemdonck <mechanix@debian.org>
Changed-By: Filip Van Raemdonck <mechanix@debian.org>
Description:
gtk-engines-eazel - Eazel engine for GTK+, with Crux theme
Closes: 123456
Changes:
eazel-engine (0.3-1) unstable; urgency=low
.
* Initial upload. Did I win the jackpot with this ITP bug number?
(Closes: #123456)
* 50build.dpatch: do not build gnome-depending capplet and test program.
* 75install.dpatch: install data in /usr/share/themes/Crux/gtk/ directory;
make sure to let this now to the engine library.
* 25config.dpatch: update config.{guess,sub} to be safe.
* 87clean.dpatch: work around braindead upstream behaviour to distribute a
generated file (the RPM spec file).
Files:
1d71f1d191d162bf3f6dc3a2b2fa64d9 640 graphics optional eazel-engine_0.3-1.dsc
4de51833278d7fa0155cc5a247e920c0 201725 graphics optional eazel-engine_0.3.orig.tar.gz
9a9391309549a9a48070155dd4ae5be9 21316 graphics optional eazel-engine_0.3-1.diff.gz
5f6b7be607cd0149651926ec338d1373 55770 graphics optional gtk-engines-eazel_0.3-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8Vak5Ejn3CY6VDgARAm6nAJwJIFxmhDQPCNUXylxkFz7QbXZn2ACghglS
Oj9WmjREyCzKObbFpJALzHk=
=nDaU
-----END PGP SIGNATURE-----
Bug unarchived.
Request was from Joost van Baal-Ilić <joostvb-debian-bugs@mdcc.cx>
to control@bugs.debian.org.
(Sun, 23 Nov 2014 05:27:04 GMT) (full text, mbox, link).
Bug archived.
Request was from Joost van Baal-Ilić <joostvb-debian-bugs@mdcc.cx>
to control@bugs.debian.org.
(Sun, 23 Nov 2014 05:48:05 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Sun Nov 19 12:41:15 2023;
Machine Name:
bembo
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.