On Sun, 12 Feb 2006 22:19:29 -0500 Mark Loeser <[EMAIL PROTECTED]>
wrote:
| I don't see this as a groundbreaking change that requires a GLEP or
| anything, especially since I eliminated most of the duplicates today,
| after talking with the respective maintainers. There are probably
| only 3 or 4
Mark Loeser wrote:
R Hill <[EMAIL PROTECTED]> said:
Anyways I just like anything that makes use.desc more useful than
foo - adds support for foo
That's really a completely separate issue. By allowing duplicate entries we
just allow people to put useless information in two places instead of o
R Hill <[EMAIL PROTECTED]> said:
> Anyways I just like anything that makes use.desc more useful than
>
> foo - adds support for foo
That's really a completely separate issue. By allowing duplicate entries we
just allow people to put useless information in two places instead of one.
--
Mark Loe
Thank you for taking the time to put preXX doc this mail together.
I find it personally inspiring and a reminder to watch how I/we handle
bugs which is often easy to overlook.
On Sun, 2006-02-12 at 21:11 +, Daniel Drake wrote:
> I wrote most of this a while ago but didn't get round to fin
Marius Mauch wrote:
On Sun, 12 Feb 2006 14:49:55 -0500
Mark Loeser <[EMAIL PROTECTED]> wrote:
On a more global scale, we should decide if this is valid though. I
haven't exactly been convinced that it is useful, but I'm not opposed
to the idea. I'd just like to see a decision one way or another
Marius Mauch <[EMAIL PROTECTED]> said:
> Yeah, unfortunately none of the people proposing the idea ever wrote a
> glep or even filed a bug regarding this (AFAIK), also as the quoted
> threads show there are a number of possible solutions for this.
It doesn't seem that too many people feel strongly
On Sun, 12 Feb 2006 14:49:55 -0500
Mark Loeser <[EMAIL PROTECTED]> wrote:
> Marius Mauch <[EMAIL PROTECTED]> said:
> > IIRC the idea behind duplication was not to use a flag for different
> > purposes, but have a generic description in use.desc (like "doc:
> > build additional docs") and give a mo
Edward Catmur wrote:
> On Sun, 2006-02-12 at 19:56 -0500, Forrest Voight wrote:
>> On 2/12/06, Donnie Berkholz <[EMAIL PROTECTED]> wrote:
>>> Forrest Voight wrote:
I was using an old gentoo system. Forget about KEYMAP.
But, what about UNICODE? That is related to KEYMAP and consolefont.
>>
On Sun, 2006-02-12 at 19:56 -0500, Forrest Voight wrote:
> On 2/12/06, Donnie Berkholz <[EMAIL PROTECTED]> wrote:
> > Forrest Voight wrote:
> > > I was using an old gentoo system. Forget about KEYMAP.
> > > But, what about UNICODE? That is related to KEYMAP and consolefont.
> > > Shouldn't EDITOR a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 12 Feb 2006, Daniel Drake wrote:
Henrik Brix Andersen wrote:
> 3. Always record contributions by name
>
> If you commit something in response to a bug report that has been filed,
> always thank the user by full name (and bug number) in
Then why can't it be in /etc/skel?
On 2/12/06, Donnie Berkholz <[EMAIL PROTECTED]> wrote:
> Forrest Voight wrote:
> > I was using an old gentoo system. Forget about KEYMAP.
> > But, what about UNICODE? That is related to KEYMAP and consolefont.
> > Shouldn't EDITOR and XSESSION be in a user-speci
Forrest Voight wrote:
> I was using an old gentoo system. Forget about KEYMAP.
> But, what about UNICODE? That is related to KEYMAP and consolefont.
> Shouldn't EDITOR and XSESSION be in a user-specific place?
I guess you didn't really understand the code. They can be in a
user-specific place.
If
I was using an old gentoo system. Forget about KEYMAP.
But, what about UNICODE? That is related to KEYMAP and consolefont.
Shouldn't EDITOR and XSESSION be in a user-specific place?
Forrest
On 2/12/06, Donnie Berkholz <[EMAIL PROTECTED]> wrote:
> Chris Gianelloni wrote:
> > On Sun, 2006-02-12 at
Chris Gianelloni wrote:
> On Sun, 2006-02-12 at 11:38 -0800, Donnie Berkholz wrote:
>> Forrest Voight wrote:
>>> Hello all,
>>>
>>>I believe that rc.conf contains many values that could be put into
>>> conf.d. For example, DISPLAYMANAGER and KEYMAP. DISPLAYMANAGER could
>>> be put into conf.d/x
Chris Gianelloni wrote:
Isn't XSESSION *only* used by display managers? I know for a fact that
it isn't used by "startx" or anything.
It is used by startx. The following commands have their expected effect:
# XSESSION="fluxbox" startx
# XSESSION="gnome" startx
Daniel
--
gentoo-dev@gentoo.org
Duncan wrote:
2. Be careful with INVALID resolutions
The term invalid _is_ harsh in bugzilla context, so make sure you write
a quick thankful-sounding comment to go with it.
I like all the suggestions, but this one hits a particular sore spot, as I
had it happen to me, with I think my second
On Sun, 2006-02-12 at 11:38 -0800, Donnie Berkholz wrote:
> Forrest Voight wrote:
> > Hello all,
> >
> >I believe that rc.conf contains many values that could be put into
> > conf.d. For example, DISPLAYMANAGER and KEYMAP. DISPLAYMANAGER could
> > be put into conf.d/xdm. Then, this variable wo
Marien Zwart wrote:
I think this is too much effort, especially for small corrections. I
tend to fix them myself, commit with a message like "...based on an
ebuild from ... (bug #)" and comment on the bug like "Committed
with minor changes". It would probably be a good thing if I went into
a
Henrik Brix Andersen wrote:
3. Always record contributions by name
If you commit something in response to a bug report that has been filed,
always thank the user by full name (and bug number) in the ChangeLog and
commit message.
Do the above even if you already knew about the bug (i.e. you w
Daniel Drake posted <[EMAIL PROTECTED]>, excerpted below, on
Sun, 12 Feb 2006 21:11:33 +:
> 2. Be careful with INVALID resolutions
>
> The term invalid _is_ harsh in bugzilla context, so make sure you write
> a quick thankful-sounding comment to go with it.
I like all the suggestions, but
On Sun, Feb 12, 2006 at 09:11:33PM +, Daniel Drake wrote:
> I wrote most of this a while ago but didn't get round to finishing it.
> This seems appropriate at this time, so here it is :)
>
> Here are some small *suggestions* for how I think we can motivate users
> on Bugzilla to contribute m
Donnie Berkholz wrote:
> Herds and people with 5 or more unported packages, and change in # of
> packages:
>
> 69 games (-20)
> 51 none (individual or no maintainer) (-6)
> 28 (no metadata.xml) (-2)
> 16 desktop-wm (-13)
> 14 video (-0)
> 11 cjk (-11)
> 7 afters
On Sunday 12 February 2006 14:16, Forrest Voight wrote:
>I believe that rc.conf contains many values that could be put into
> conf.d.
sounds like your system is outdated
> For example, DISPLAYMANAGER
Donnie already covered this
> and KEYMAP.
this was moved to /etc/conf.d/keymaps a while ag
Hi,
On Sun, Feb 12, 2006 at 09:11:33PM +, Daniel Drake wrote:
> 2. Be careful with INVALID resolutions
>
> The term invalid _is_ harsh in bugzilla context, so make sure you write
> a quick thankful-sounding comment to go with it.
>
> Maybe we should consider alternatives. I quite like the N
I wrote most of this a while ago but didn't get round to finishing it.
This seems appropriate at this time, so here it is :)
Here are some small *suggestions* for how I think we can motivate users
on Bugzilla to contribute more, and to contribute more often. I'm not
suggesting this be enforced
o.org/~spyderous/broken_modular/broken_modular_maintainers.txt.20060212
Herds and people with 5 or more unported packages, and change in # of
packages:
69 games (-20)
51 none (individual or no maintainer) (-6)
28 (no metadata.xml) (-2)
16 desktop-wm (-13)
14 video (-0)
1
Marius Mauch <[EMAIL PROTECTED]> said:
> IIRC the idea behind duplication was not to use a flag for different
> purposes, but have a generic description in use.desc (like "doc: build
> additional docs") and give a more detailed description in
> use.local.desc (like "doc: build API docs and manual a
Forrest Voight wrote:
> Hello all,
>
>I believe that rc.conf contains many values that could be put into
> conf.d. For example, DISPLAYMANAGER and KEYMAP. DISPLAYMANAGER could
> be put into conf.d/xdm. Then, this variable would not exist with a
> non-X environment, and configuration could be m
Hello all,
I believe that rc.conf contains many values that could be put into
conf.d. For example, DISPLAYMANAGER and KEYMAP. DISPLAYMANAGER could
be put into conf.d/xdm. Then, this variable would not exist with a
non-X environment, and configuration could be more modularized.
Forrest Voight
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 12 Feb 2006, Michael Hanselmann wrote:
Hello Patrick
On Sun, Feb 12, 2006 at 06:42:01PM +0100, Patrick Lauer wrote:
In what range do you need the random numbers?
For this ebuild, lower than 1000.
Um, there are 167 primes smaller that
On Sun, 12 Feb 2006 17:49:26 +0100
Simon Stelling <[EMAIL PROTECTED]> wrote:
> R Hill wrote:
> > a global USE flag duplicated in use.local.desc could be used to
> > give specific information about exactly what effect the flag has on
> > a certain package, or if for some reason it does differ sligh
Hello
On Sun, Feb 12, 2006 at 06:22:00PM +0100, Michael Hanselmann wrote:
> [prime.eclass]
After discussing it with Simon Stelling (blubb), I decided to put the
code into the ebuild directly for now. Since this is experimental stuff,
that's no problem for now. The code will be moved to an eclass
Michael Hanselmann wrote:
>> In what range do you need the random numbers?
>
> For this ebuild, lower than 1000.
>
>> And I guess a 32-bit prime is out of reach :-)
>
> Indeed.
So maybe use a precomputed table of primes <1000 ?
--
Krzysiek Pawlik key id: 0xBC51
desktop-misc, desktop-
On Sunday 12 February 2006 12:22, Michael Hanselmann wrote:
> For an ebuild I'm working on, I need a function to test wether a number
> is a prime number. For that, I wrote an Eclass you find attached to this
> e-mail. Can this be commited?
i cant really see how this would be useful to anything, b
Hello Patrick
On Sun, Feb 12, 2006 at 06:42:01PM +0100, Patrick Lauer wrote:
> In what range do you need the random numbers?
For this ebuild, lower than 1000.
> And I guess a 32-bit prime is out of reach :-)
Indeed.
Greets,
Michael
--
Gentoo Linux developer, http://hansmi.ch/, http://forkbomb
On Sun, 2006-02-12 at 18:22 +0100, Michael Hanselmann wrote:
> Hello
>
> For an ebuild I'm working on, I need a function to test wether a number
> is a prime number. For that, I wrote an Eclass you find attached to this
> e-mail. Can this be commited?
In what range do you need the random numbers?
Hello
For an ebuild I'm working on, I need a function to test wether a number
is a prime number. For that, I wrote an Eclass you find attached to this
e-mail. Can this be commited?
Thanks,
Michael
--
Gentoo Linux developer, http://hansmi.ch/, http://forkbomb.ch/
We apologize for the inconvenien
R Hill wrote:
> a global USE flag duplicated in use.local.desc could be used to give specific
> information about exactly what effect the flag has on a certain package, or if
> for some reason it does differ slightly from the global meaning.
>
> global use flags (searching: doc)
>
Ciaran McCreesh wrote:
> On Sun, 12 Feb 2006 03:19:25 -0500 Mark Loeser <[EMAIL PROTECTED]>
> wrote:
> | So, what do we want to do about this? Should we have some repoman
> | warning if a USE flag exists in both files, or should it be
> | acceptable?
>
> The whole idea of global USE flags is that
PROFILE_ARCH is currently used for various sub-architectures (e.g.
sparc32 vs sparc64, 32 bit ppc vs ppc64, xbox vs normal x86) that don't
have their own keyword but that do occasionally need special behaviour.
It can be used in conditionals, but because no-one ever quite got
around to it, it *can'
On Sun, 12 Feb 2006 03:19:25 -0500 Mark Loeser <[EMAIL PROTECTED]>
wrote:
| So, what do we want to do about this? Should we have some repoman
| warning if a USE flag exists in both files, or should it be
| acceptable?
The whole idea of global USE flags is that they're the same for all
packages th
Well, the subject really says it all. On bug #89056 it seems to be thought
that the duplication is not necessarily a bad thing. I'm not sure this is
such a great idea myself, since if the USE flag needs a separate description
for a package, it means that the behaviour from that flag could be diff
42 matches
Mail list logo
