On Thu, 2008-10-02 at 22:24 +0200, Jeroen Roovers wrote:
# Gen 2 Developer [EMAIL PROTECTED] (`date`)
# Masked for testing.
=rofl-cat/omgpkg-ver
Please people,
if you want to get something tested, then don't mask it.
Stuff with high impact better be masked for initial testing,
On Thu, Oct 2, 2008 at 8:16 PM, Jeroen Roovers [EMAIL PROTECTED] wrote:
On Fri, 3 Oct 2008 04:23:33 +0200
Dawid Węgliński [EMAIL PROTECTED] wrote:
I don't think it's ok. ~arch isn't training ground. It's supposed to
work, so asking arch teams to keywords packages that are not supposed
to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
This is a revised version of the PROPERTIES=set proposal which has
been discussed previously [1].
Please consider a PROPERTIES=set value will serve to indicate that a
given ebuild should be exposed within the package set framework as a
* Robin H. Johnson [EMAIL PROTECTED]:
On Fri, Oct 03, 2008 at 07:33:11AM +0200, Torsten Veller wrote:
* Robin H. Johnson [EMAIL PROTECTED]:
And something is broken with CPAN, just in time for us :-).
Manually browsing give me:
http://search.cpan.org/~rjbs/Email-MessageID-1.400/
Mart Raudsepp [EMAIL PROTECTED] posted [EMAIL PROTECTED],
excerpted below, on Fri, 03 Oct 2008 10:06:39 +0300:
Of course when that initial testing is done with helping users, the
reason could be modified to tell things broke and what the tracking bug
is, or unmasked if it works fine with
Alec Warner schrieb:
On Thu, Oct 2, 2008 at 8:16 PM, Jeroen Roovers [EMAIL PROTECTED] wrote:
On Fri, 3 Oct 2008 04:23:33 +0200
Dawid Węgliński [EMAIL PROTECTED] wrote:
I don't think it's ok. ~arch isn't training ground. It's supposed to
work, so asking arch teams to keywords packages that
On Fri, 03 Oct 2008 00:10:56 -0700
Zac Medico [EMAIL PROTECTED] wrote:
For the new sets profile configuration file format, the simplest
possible layout could have a set name in the first column and a
package atom in the second column. The package atom should match an
ebuild which exhibits the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
On Fri, 03 Oct 2008 00:10:56 -0700
Zac Medico [EMAIL PROTECTED] wrote:
For the new sets profile configuration file format, the simplest
possible layout could have a set name in the first column and a
package atom in the
Hi,
welcome to your mentor reviews. :)
Heath Caldwell (hncaldwell) [EMAIL PROTECTED]:
Index: metadata.xml
flag name=kakasi
Enable pkgapp-i18n/kakasi/pkg support for
furigana generation /flag
I tend to call it furigana instead of kakasi, as USE flags
On Fri, Oct 3, 2008 at 5:06 AM, Thomas Sachau [EMAIL PROTECTED] wrote:
Alec Warner schrieb:
On Thu, Oct 2, 2008 at 8:16 PM, Jeroen Roovers [EMAIL PROTECTED] wrote:
On Fri, 3 Oct 2008 04:23:33 +0200
Dawid Węgliński [EMAIL PROTECTED] wrote:
I don't think it's ok. ~arch isn't training ground.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
Please consider a new eapi profile configuration file that will
designate the EAPI to which any package atoms within a given layer
of the profile stack must conform. This will allow package managers
to bail out with an informative error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zac Medico wrote:
Hi everyone,
This is a revised version of the PROPERTIES=set proposal which has
been discussed previously [1].
snip a detailed proposal about a new kind of set
Let me try show some real examples of the type of sets I would
On Thu, 2 Oct 2008 22:24:35 +0200
Jeroen Roovers [EMAIL PROTECTED] wrote:
Please people,
if you want to get something tested, then don't mask it.
Um... no? One thing that package.mask has always been used for is
temporarily masking a package until it can be tested and then unleashed
on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
This is a revised version of the PROPERTIES=set proposal which has
been discussed previously [1].
Please consider a PROPERTIES=set value will serve to indicate that a
given ebuild should be exposed within the package set framework as a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
Please consider a new eapi profile configuration file that will
designate the EAPI to which any package atoms within a given layer
of the profile stack must conform. This will allow package managers
to bail out with an informative error
--
-BEGIN PGP SIGNED MESSAGE-
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
--
--
END OF COMMANDS
Somebody subscribed a bad list manager to the list, and caused a mail
loop. I removed the offending list address now, but I don't know who did
it in the first place.
--
Robin Hugh Johnson
Gentoo Linux Developer Infra Guy
E-Mail : [EMAIL PROTECTED]
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E
64 matches
Mail list logo
