-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I know there was an announcement about the upcoming change to
cmake-utils.eclass, however... it is not enough to give a deadline
without caring if people actually fixed it by then.
By doing that you risk breaking stable packages which is not trivial.
On 18:52 Mon 08 Jul , Pavlos Ratis wrote:
> As far as I can see, opinions about VCs are 50-50. However, I don't
> see any disadvantages adding video hangouts to the project. VCs _are
> not_ mandatory and doesn't replace any of our current communication
> methods. You are not forced to participa
On 20:19 Thu 04 Jul , Mike Pagano wrote:
> I have 'relaxed' a tad about what I think should be in g-s, but maybe it has
> gone a bit farther than I wanted it too.
>
> I would like to see a "-experimental" use flag and base,extras,geek
> (whatever)
> so that g-s goes back to what it's origin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/17/2013 04:57 PM, hasufell wrote:
> I know there was an announcement about the upcoming change to
> cmake-utils.eclass, however... it is not enough to give a deadline
> without caring if people actually fixed it by then.
>
> By doing that you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/17/2013 05:17 PM, Chris Reffett wrote:
> On 07/17/2013 04:57 PM, hasufell wrote:
>> I know there was an announcement about the upcoming change to
>> cmake-utils.eclass, however... it is not enough to give a deadline
>> without caring if people
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/17/2013 11:28 PM, Rick "Zero_Chaos" Farina wrote:
> On 07/17/2013 05:17 PM, Chris Reffett wrote:
>> On 07/17/2013 04:57 PM, hasufell wrote:
>>> I know there was an announcement about the upcoming change to
>>> cmake-utils.eclass, however... it i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/17/2013 05:34 PM, hasufell wrote:
> On 07/17/2013 11:28 PM, Rick "Zero_Chaos" Farina wrote:
>> On 07/17/2013 05:17 PM, Chris Reffett wrote:
>>> On 07/17/2013 04:57 PM, hasufell wrote:
I know there was an announcement about the upcoming chang
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/17/2013 11:42 PM, Rick "Zero_Chaos" Farina wrote:
> On 07/17/2013 05:34 PM, hasufell wrote:
>> On 07/17/2013 11:28 PM, Rick "Zero_Chaos" Farina wrote:
>>> On 07/17/2013 05:17 PM, Chris Reffett wrote:
On 07/17/2013 04:57 PM, hasufell wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/17/2013 05:47 PM, hasufell wrote:
> On 07/17/2013 11:42 PM, Rick "Zero_Chaos" Farina wrote:
>> On 07/17/2013 05:34 PM, hasufell wrote:
>>> On 07/17/2013 11:28 PM, Rick "Zero_Chaos" Farina wrote:
On 07/17/2013 05:17 PM, Chris Reffett wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/17/2013 11:55 PM, Rick "Zero_Chaos" Farina wrote:
>
>
> It is my understanding that if you directly use a function from an
> eclass you are REQUIRED to inherit that eclass. Given that kind
> of sanity would have prevented these failures I fin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 17 Jul 2013 23:34:36 +0200
hasufell wrote:
> That means the methods for eclass changes must be more thoroughly.
So must the methods to write ebuilds be more thoroughly; therefore, I
think that we can somewhat build a script that checks this
11 matches
Mail list logo