From: "Jorge Peixoto de Morais Neto" <please.no.spam.here@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] e17 overlay bug
Date: Tue, 4 Nov 2008 11:36:54 -0200 [thread overview]
Message-ID: <38af3d670811040536ga03bbddic628f4f6e0fa3253@mail.gmail.com> (raw)
In-Reply-To: <200811041054.24532.alan.mckinnon@gmail.com>
>> I've found that the recent EINA library release for e17 has broken just
>> about everything.
>>
>> Gentoo's overlay system should be simple enough to modify however after
>> reading the fine manual I am no closer to understanding the appropriate
>> course of action to create eina as a dependency in the overlay (I've bugged
>> vapier@gentoo.org to no avail)
>
> Mike is usually pretty quick with these things.
"Mike"?!, What, Vapier's formal name is "Mike"?
Back to important stuff, is the overlay in good shape (apart from
this specific problem)? For example, is it compatible with Portage's
new requirements for Manifest?
Also, why are the snapshot ebuilds so horribly outdated? Is it because
Vapier is too busy to update them or because he just thinks that e17
is like Mplayer, a project where the developers actually take care to
keep the svn code in good shape (only committing working code)?
My computer has some bugs*. I am trying Xfce instead of e17 to see if
the bugs were e17's fault, but the bugs continue. I wonder if I should
go back to e17
1) It is *very* fast and *very* lightweight (even when compared to Xfce)
2) It is vastly configurable and does things Xfce does not (like, for
a quick example, remembering per-window configuration, fine tuning
window borders, and even making windows borderless)
but
1) It is unreleased; users have to compile code from svn.
2) Outputs a truckload of text to .xsession-errors. Does it mean that
the code is full of little problems that cause warnings? Xfce, in
comparison, only outputs two "assertion failed"s
3) Does not seem to have a Trash Bin or a System tray. I care little
about these, though (and I imagine there are plugins to provide them,
but I didn't bother to search).
Do you think a user who expects a reasonably stable and bug-free
environment (say, a user who accepts the latest Ubuntu, instead of
demanding the stability of Debian stable) can rely on e17?
*Regarding my bugs, they are mostly X-related. When I have time I will
dive in xorg.conf documentation. Also, maybe they are related to the
fact that some of my X-related packages may have been built with
different USE flags (I have disabled the IPv6 USE flag at some point).
I will recompile them all, either when Gentoo updates Xorg (which, by
the way, is taking a long time) or when Gentoo updates GCC (which is
also taking a very long time. I hope that when Debian Stable is
released with GCC 4.3, it will motivate Gentoo to declare GCC 4.3.2
stable).
--
Software is like sex: it is better when it is free - Linus Torvalds
next prev parent reply other threads:[~2008-11-04 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 8:38 [gentoo-user] e17 overlay bug Hazen Valliant-Saunders
2008-11-04 8:54 ` Alan McKinnon
2008-11-04 13:36 ` Jorge Peixoto de Morais Neto [this message]
2008-11-04 13:42 ` Hazen Valliant-Saunders
2008-11-04 15:57 ` Alan McKinnon
2008-11-04 15:45 ` Alan McKinnon
2008-11-04 17:45 ` Jorge Peixoto de Morais Neto
2008-11-08 3:35 ` Hal Martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38af3d670811040536ga03bbddic628f4f6e0fa3253@mail.gmail.com \
--to=please.no.spam.here@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox