From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: tabbed x11-terms/rxvt-unicode
Date: Sat, 8 Oct 2011 21:23:57 +0200 [thread overview]
Message-ID: <20111008212357.58e71946@rohan.example.com> (raw)
In-Reply-To: <201110082109.48249.francesco.talamona@know.eu>
On Sat, 8 Oct 2011 21:09:48 +0200
Francesco Talamona <francesco.talamona@know.eu> wrote:
> On Saturday 08 October 2011, Michael Orlitzky wrote:
> > On 10/08/11 13:43, Francesco Talamona wrote:
> > > x11-terms/rxvt-unicode is one of the program I use the most, today
> > > I lost the ability to have multiple tabs and almost panicked.
> > >
> > > I found the solution to have back this essential feature:
> > > re-enable "perl" USE flag for this package and re-emerge.
> > >
> > > Just wanted to share my experience.
> > > HTH
> >
> > I'm going to start a bug-filing campaign against packages like this
> > some day. The only description we ever get for use flag foo is
> > 'enable support for foo', which doesn't tell you anything at all
> > about how it affects a given package.
> >
> > There are a number of packages with perl and python use flags where
> > disabling the use flag will silently disable essential
> > functionality. In my opinion, the use flag should simply be removed
> > rather than have what amounts to USE=make_it_work_properly.
> >
> > I agree with the (default) removal of the perl and python flags:
> >
> > http://blog.jolexa.net/
> >
> > but you should complain about packages that are basically broken
> > without them.
>
> I'm not going to complain, though I'm willing to point out (e.g.
> commenting on relevant bug reports) that some packages are affected
> in a bad way by this move.
>
> To be honest I didn't look for a solution in b.g.o because it was
> straightforward; even if not so manifest for me the link between the
> perl flag and the ability for rxvt to run tabbed (given that it
> doesn't give an error).
>
> I don't want to be blunt, but your plan looks to me quite vague.
> My opinion is that some packages should have a different default.
A good plan is to give USE flags sensible names. This one describes
what the flag *is*, a good description tells you what the flag *does*.
"USE=perl" tells you squat, you don't even know what effect it will
have. You'd have to read the ebuild and the source to figure that out.
A MUCH better name is "USE=tabs" with a description like this "Provide
multiple tabs, requires perl."
It's really just a different manifestation of the #1 but in almost all
interfaces: exposing the underlying implementation in the interface.
--
Alan McKinnnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2011-10-08 19:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 17:43 [gentoo-user] tabbed x11-terms/rxvt-unicode Francesco Talamona
2011-10-08 18:43 ` Michael Orlitzky
2011-10-08 19:09 ` [gentoo-user] " Francesco Talamona
2011-10-08 19:23 ` Alan McKinnon [this message]
2011-10-08 20:34 ` Willie Matthews
2011-10-09 16:48 ` James Cloos
2011-10-09 17:53 ` Alan McKinnon
2011-10-09 18:58 ` Michael Orlitzky
2011-10-10 1:06 ` Pandu Poluan
2011-10-11 17:58 ` Francesco Talamona
2011-10-12 15:30 ` Michael Orlitzky
2011-10-08 20:59 ` Michael Orlitzky
2011-10-11 17:51 ` Francesco Talamona
2011-10-11 18:19 ` Francesco Talamona
2011-10-10 22:46 ` [gentoo-user] " Peter Humphrey
2011-10-11 17:50 ` [gentoo-user] " Francesco Talamona
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=20111008212357.58e71946@rohan.example.com \
--to=alan.mckinnon@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