[gentoo-dev] [liveebuild] Standard eclass interface for vcs

2008-06-16 Thread Luca Barbato
Something I'd like to have to ease the live template implementation would be a standardized eclass interface for every vcs, right now every eclass does more or less the same things BUT with slight differences and obviously with different names. Now, I'd like to know which interface you'd consi

Re: [gentoo-dev] Re: Default blank lines for error, elog, einfo, etc

2008-06-16 Thread Jim Ramsay
Joe Peterson <[EMAIL PROTECTED]> wrote: > As for why it would be more useful than eerror/ewarn without an > argument: it would potentially allow for intelligent "context-based" > coloring of the "*" (based on surrounding lines). Well, this is true and it isn't... In the case of: ewarn line one

Re: [gentoo-dev] Re: Default blank lines for error, elog, einfo, etc

2008-06-16 Thread Jim Ramsay
"Benedikt Morbach" <[EMAIL PROTECTED]> wrote: > On Sun, Jun 15, 2008 at 12:02 PM, Peter Volkov <[EMAIL PROTECTED]> wrote: > > But speaking about names of options - -A and -B are easier to > > remember as -A stands for above and -B for below and grep users > > already knew that. > > for grep -A me

[gentoo-dev] OT: OpenRC - thanks Roy

2008-06-16 Thread Ed W
Hi, bit off topic, but there hasn't been much discussion of the OpenRC progress recently - I just wanted to say a bit thanks to Roy for his work on this - it's been working well on my vservers for a good few months now, but I hadn't realised just how fast it was until I converted my mythtv box

[gentoo-dev] Re: Default blank lines for error, elog, einfo, etc

2008-06-16 Thread Duncan
Jim Ramsay <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Mon, 16 Jun 2008 08:34:01 -0400: > Joe Peterson <[EMAIL PROTECTED]> wrote: >> As for why it would be more useful than eerror/ewarn without an >> argument: it would potentially allow for intelligent "context-based" >> col

Re: [gentoo-dev] Re: Default blank lines for error, elog, einfo, etc

2008-06-16 Thread Joe Peterson
Duncan wrote: > Jim Ramsay <[EMAIL PROTECTED]> posted > [EMAIL PROTECTED], excerpted below, on Mon, 16 > Jun 2008 08:34:01 -0400: > >> Well, this is true and it isn't... In the case of: >> >> ewarn line one >> eblank >> ewarn line two >> >> Obviously it would be the same as ewarn. However,

[gentoo-dev] Re: Default blank lines for error, elog, einfo, etc

2008-06-16 Thread Duncan
Joe Peterson <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Mon, 16 Jun 2008 10:41:55 -0600: > I am leaning more and more toward the idea of a neutral color for > eblanks, as this would indeed be trivial to code and it would make > output make more sense, especially for conditi

Re: [gentoo-dev] Re: Default blank lines for error, elog, einfo, etc

2008-06-16 Thread William L. Thomson Jr.
On Sun, 2008-06-15 at 14:02 +0400, Peter Volkov wrote: > В Срд, 11/06/2008 в 19:45 -0400, Jim Ramsay пишет: > > Vlastimil Babka <[EMAIL PROTECTED]> wrote: > > > > > I would prefer something that > > > doesn't add extra lines to ebuild. > > > > I think I would disagree with you here. I think tha

Re: [gentoo-dev] Re: Default blank lines for error, elog, einfo, etc

2008-06-16 Thread William L. Thomson Jr.
On Mon, 2008-06-16 at 17:01 +, Duncan wrote: > Joe Peterson <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], > excerpted below, on Mon, 16 Jun 2008 10:41:55 -0600: > > > I am leaning more and more toward the idea of a neutral color for > > eblanks, as this would indeed be trivial to code and it

[gentoo-dev] tetex maintainance (RFH?)

2008-06-16 Thread Alexis Ballier
Dear all, app-text/tetex is currently assigned to tex as maintainer, but, in my opinion, that's a lie. I have not seen any movement on tetex bugs for a while. I have opened a tracker bug (#227443, [1]), if someone feels the courage of picking it up. I don't have neither the time nor the will to do

Re: [gentoo-dev] Re: Nominations open for the Gentoo Council 2008/2009

2008-06-16 Thread Mart Raudsepp
On N, 2008-06-05 at 17:34 +0200, Diego 'Flameeyes' Pettenò wrote: > "Łukasz Damentko" <[EMAIL PROTECTED]> writes: > > > Nominations for the Gentoo Council 2008/2009 are open now and will be > > open for the next two weeks (until 23:59 UTC, 18/06/2008). > > I wish to nominate Halcy0n, Cardoe and l

[gentoo-dev] Re: tetex maintainance (RFH?)

2008-06-16 Thread Ryan Hill
On Mon, 16 Jun 2008 19:57:45 +0200 Alexis Ballier <[EMAIL PROTECTED]> wrote: > The other option is to p.mask and last rite it, breaking mips and s390 > trees, leaving them without tex support at all. This would also > leave arm and sh with only ptex as tex support. Thus that is not > really an opt

[gentoo-dev] Re: A few questions to our nominees

2008-06-16 Thread Ryan Hill
On Sat, 14 Jun 2008 22:16:36 +0200 Luca Barbato <[EMAIL PROTECTED]> wrote: > Bernd Steinhauser wrote: > > Wow, impressive. > > > > Actually, you can't be serious... > > I am. > > GLEP 54 for quite some time now and it works very well. > > adds nothing to - and sets usage as is. > > I just d

[gentoo-dev] Re: Council nominations deadline

2008-06-16 Thread Ryan Hill
On Sun, 15 Jun 2008 12:16:00 + "Jorge Manuel B. S. Vicetto" <[EMAIL PROTECTED]> wrote: The current nominees and the state of their acceptance can > be checked on > http://www.gentoo.org/proj/en/council/voting-logs/council-2008-nominees.xml > If there's someone else you would like to nominate

Re: [gentoo-dev] Re: tetex maintainance (RFH?)

2008-06-16 Thread Alexis Ballier
On Mon, 16 Jun 2008 20:45:35 -0600 Ryan Hill <[EMAIL PROTECTED]> wrote: > On Mon, 16 Jun 2008 19:57:45 +0200 > Alexis Ballier <[EMAIL PROTECTED]> wrote: > > > The other option is to p.mask and last rite it, breaking mips and > > s390 trees, leaving them without tex support at all. This would also