On Wed, Jun 11, 2014 at 10:34 AM, Rich Freeman wrote:
> We have a git repo now. We can generate one at any time. We still
> don't have infra tools.
>
> I don't know if the repo is published anywhere, but there are plenty
> of bundles on dev.gentoo.org:/space/git-work/
So, if anybody does want t
On Wed, Jun 11, 2014 at 8:54 AM, Alex Xu wrote:
>
> https://bugs.gentoo.org/show_bug.cgi?id=333701:
>> What comment #2 should have said: "This bug is so low priority to the
>> overall initiative that there shouldn't be anyone considering it a
>> blocker, show me the git repo then we can talk" :)
>
Michał Górny schrieb:
> Dnia 2014-06-11, o godz. 15:30:26
> Chí-Thanh Christopher Nguyễn napisał(a):
>
>>> 3. There is no clean way of enforcing SSL provider match between
>>> packages. Wasn't this thread initially about curl and rtmpdump
>>> requiring matching flags?
>> It could be enforced if an
Dnia 2014-06-11, o godz. 15:30:26
Chí-Thanh Christopher Nguyễn napisał(a):
> > 3. There is no clean way of enforcing SSL provider match between
> > packages. Wasn't this thread initially about curl and rtmpdump
> > requiring matching flags?
>
> It could be enforced if an eclass does the actual c
On Wed, Jun 11, 2014 at 4:38 PM, Sergey Popov wrote:
> 11.06.2014 04:48, Duy Nguyen пишет:
>> On Wed, Jun 11, 2014 at 5:59 AM, Patrick Lauer wrote:
>>> Another part: Git wasn't ready.
>>> The first migration attempt failed after consuming nearly 100GB of RAM!
>>> When it did work it took obscene
Michał Górny schrieb:
>>
>> I don't like this. If the user specifies several SSL providers in
>> make.conf, it should mean that any of these is fine and the ebuild can
>> choose an arbitrary one. The exactly-one-of operator would cause emerge
>> to complain in this case and possibly force the user
On Tue, 10 Jun 2014 21:47:50 -0600
Ryan Hill wrote:
> v2: Restrict by arch
> --
>
> Title: GCC 4.8.3 defaults to -fstack-protector
> Author: Ryan Hill
> Content-Type: text/plain
> Posted: 2014-06-10
> Revision: 1
> News-Item-Format: 1.0
> Display-If-Installed: >=sys-devel/gcc-4.8.3
> Display-If
Dnia 2014-06-11, o godz. 13:12:38
Chí-Thanh Christopher Nguyễn napisał(a):
> > REQUIRED_USE="
> > curl_ssl_winssl? ( elibc_Winnt )
> > ssl? (
> > ^^ (
> > [...]
> > )
> > )"
>
> I don't like this. If the user specifies several SSL providers in
> make.conf, it should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/06/14 18:45, Andrew Savchenko wrote:
> Why are you saying that git is inefficient with large projects?
Because it is.
> It was developed with efficiency in mind in the first place.
Not for big projects.
> And kernel guys will likely disagree
On 10/06/14 06:59 PM, Patrick Lauer wrote:
> [snip]
https://bugs.gentoo.org/show_bug.cgi?id=333531
> The current state is almost usable, but it is still obscenely slow
> (e.g. initial clone taking ~10 CPU-minutes just to figure out what to
> do), but we can just throw more hardware at it.
https:
On Wed, Jun 11, 2014 at 12:17 AM, Patrick Lauer wrote:
> Now git has some/all of the needed features, and people wait on a future
> potential git migration instead of figuring out the important bits now
> (a good part of that is defined in GLEP 63, but there's no action apart
> from work on gentoo
On 06/11/14 07:12, Chí-Thanh Christopher Nguyễn wrote:
Dear all,
I'm a bit late to the party, but here is my $0.02:
REQUIRED_USE="
curl_ssl_winssl? ( elibc_Winnt )
ssl? (
^^ (
[...]
)
)"
I don't like this. If the user specifies several SSL providers in
make.co
Dear all,
I'm a bit late to the party, but here is my $0.02:
> REQUIRED_USE="
> curl_ssl_winssl? ( elibc_Winnt )
> ssl? (
> ^^ (
> [...]
> )
> )"
I don't like this. If the user specifies several SSL providers in
make.conf, it should mean that any of these is fine and
11.06.2014 04:48, Duy Nguyen пишет:
> On Wed, Jun 11, 2014 at 5:59 AM, Patrick Lauer wrote:
>> Another part: Git wasn't ready.
>> The first migration attempt failed after consuming nearly 100GB of RAM!
>> When it did work it took obscene amounts of time, and the result was
>> unusably large (e.g.
14 matches
Mail list logo
