Joe Peterson <[EMAIL PROTECTED]> posted [EMAIL PROTECTED],
excerpted below, on Tue, 19 Aug 2008 15:45:11 -0600:
> Ah, OK. I have been considering that "world" is simply a grandfathered
> name for "@world" (and same for system). I.e. that "world" is also
> specifying the world set, but that only
Steve Long wrote:
>> @system == system
>> ...but...
>> @world != world
>>
>> This, I would think, could cause confusion too - and we'd have to live
>> with and document this "quirk".
>>
> I don't see that as major from a user pov; as soon as you see @ you're in
> set territory, which is for finer-g
On Tue, 19 Aug 2008 21:27:03 +0100
Steve Long <[EMAIL PROTECTED]> wrote:
> > On Tue, 19 Aug 2008 23:31:17 +0530
> > Arun Raghavan <[EMAIL PROTECTED]> wrote:
> >> Ciaran McCreesh wrote:
> >> > The benefit is that it's a logically separate action, and will
> >> > avoid all the silliness of people rep
Ciaran McCreesh wrote:
> On Tue, 19 Aug 2008 23:31:17 +0530
> Arun Raghavan <[EMAIL PROTECTED]> wrote:
>> Ciaran McCreesh wrote:
>> > The benefit is that it's a logically separate action, and will avoid
>> > all the silliness of people repeatedly changing their minds about
>> > which phase should
Joe Peterson wrote:
> Duncan wrote:
>> That's an interesting idea. I don't personally care either way, as long
>> as @world continues to /not/ include system/@system, but having world
>> (without the @) continue to include system /would/ be useful for backward
>> compatibility. I think it'd be m
On Tuesday 19 August 2008, Mark Loeser wrote:
> I am not sure how we would be able to enforce this across the board
> for forcefully retired developers.
If we are talking policies, can someone please define the
term 'forecefully retired'? What about people whom had been complained
about to devre
On Tue, 19 Aug 2008 23:31:17 +0530
Arun Raghavan <[EMAIL PROTECTED]> wrote:
> Ciaran McCreesh wrote:
> > The benefit is that it's a logically separate action, and will avoid
> > all the silliness of people repeatedly changing their minds about
> > which phase should do the eautoreconf calls and so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
[...]
> The benefit is that it's a logically separate action, and will avoid
> all the silliness of people repeatedly changing their minds about
> which phase should do the eautoreconf calls and so on.
a) Is this really an issue
Hello.
There are droid fonts package in the tree. Author states that they are
apache licensed [1] (supposedly similar to google's android sdk) but
license itself is not included in the package (only .ttf files are
there). Should we RESTRICT="mirror" in such case or it's safe to drop
such restricti
On Tue, Aug 19, 2008 at 12:12 PM, Steve Long
<[EMAIL PROTECTED]> wrote:
> Ciaran McCreesh wrote:
>> If you're doing new phases... Exheres has been using src_prepare, after
>> src_unpack, to avoid having lots of things of the form:
>>
>> src_unpack() {
>> default
>> patch blah
>> eautore
Duncan wrote:
> That's an interesting idea. I don't personally care either way, as long
> as @world continues to /not/ include system/@system, but having world
> (without the @) continue to include system /would/ be useful for backward
> compatibility. I think it'd be much better in terms of e
On Tue, Aug 19, 2008 at 9:16 AM, Tobias Scherbaum <[EMAIL PROTECTED]>wrote:
> Mark Loeser wrote:
> > I personally don't see why they should be allowed to stay part of our
> > communication channels where they have caused problems bad enough to get
> > them retired. With that being said, I think t
Mark Loeser wrote:
> Lukasz Damentko <[EMAIL PROTECTED]> said:
> > 1. I'd like to ask Council to discuss possible reactions to our [...]
> Due to their privacy policy I don't think we'll ever be able to get
> adequate explanations from Freenode staff when our devs are banned.
I think that's a lim
Mark Loeser wrote:
> I personally don't see why they should be allowed to stay part of our
> communication channels where they have caused problems bad enough to get
> them retired. With that being said, I think the same technical issues
> come into play here as with banning someone from "Gentoo"
Hi All.
I have some information for those of you using Ada on this list (it appears
there are quite a few, so, please drop those "all two people using.."
jokes ;)).
I have found that the recently released -2008 version has some "incompatible
bugs" with the -2007 version (NB: this is gnat-gpl,
Steve Long <[EMAIL PROTECTED]> posted
[EMAIL PROTECTED], excerpted below, on Tue, 19 Aug 2008 09:20:00
+0100:
> I think there's a good case for system and world without the set
> specifier working the way they always have. I for one am very aware if I
> type in @world (ie not system, useful for -
Ciaran McCreesh wrote:
> On Wed, 13 Aug 2008 01:18:33 -0700
> Zac Medico <[EMAIL PROTECTED]> wrote:
>> * The old src_compile phase function is split into separate
>>src_configure and src_compile fuctions.
>
> If you're doing new phases... Exheres has been using src_prepare, after
> src_unpac
Ali Polatel yazmış:
> Now that the packages depending on 2.3 are masked, masking this one
> again for removal in 30 days.
>
I've moved python-2.3 from gentoo-x86 to python junkyard overlay¹.
¹: http://overlays.gentoo.org/proj/python/browser/overlays/junkyard
--
Regards,
Ali Polatel
pgpB3R7i4
Duncan wrote:
>every time I try to emerge -NuD system
I think there's a good case for system and world without the set specifier
working the way they always have. I for one am very aware if I type in
@world (ie not system, useful for -e) vs world. I don't see any benefit to
the user in jettisonin
19 matches
Mail list logo
