Le 12/11/2013 22:12, Robert Bradshaw a écrit :
> Writing code that works against, for example, multiple versions of
> Python takes extra care, as does testing it. Expand this to many
> different libraries and one has a full cross product of possible
> failure modes. Couple that with the (like it or
On Tue, Nov 12, 2013 at 11:20 AM, Abdó Roig-Maranges
wrote:
>
> Hi
>
> mich...@orlitzky.com writes:
>
>> * Bundling libraries are terrible for security. I should be able to
>> open a PNG in code that I myself wrote, without worrying about a
>> buffer overflow. My distro patches these hol
Le 12/11/2013 12:33, Volker Braun a écrit :
> On Monday, November 11, 2013 11:55:56 PM UTC-8, Snark wrote:
>
> example: disabling threading in ecl
>
>
> Perhaps the scope of the Sage project is different from that of an
> embedded Lisp interpreter?
My point was:
(1) sage uses ECL for some
On Tue, Nov 12, 2013 at 11:20 AM, Abdó Roig-Maranges
wrote:
>
> Hi
>
> mich...@orlitzky.com writes:
>
>> * Bundling libraries are terrible for security. I should be able to
>> open a PNG in code that I myself wrote, without worrying about a
>> buffer overflow. My distro patches these hol
Hi
mich...@orlitzky.com writes:
> * Bundling libraries are terrible for security. I should be able to
> open a PNG in code that I myself wrote, without worrying about a
> buffer overflow. My distro patches these holes immediately. Sage
> doesn't, there's just not enough manpower.
>
On 11/12/2013 07:00 PM, Michael Orlitzky wrote:
> Yes, yes, and yes. But there's more:
Oh... I only wondered why Sage from github wants to install its own git.
But this thread seems to develop into a discussion of some people that
like a monolithic we-redo-all-ourselves sage and some that like mor
On 11/12/2013 12:29 PM, Robert Bradshaw wrote:
>> This is maddening.
>
> Why is this so maddening? Are you out of room on your hard drive? It
> took too long to build? It offends your sense of aesthetics?
Yes, yes, and yes. But there's more:
* Bundling libraries are terrible for security. I sh
On Mon, Nov 11, 2013 at 11:55 PM, Julien Puydt wrote:
> Le 11/11/2013 20:45, Robert Bradshaw a écrit :
>> On Mon, Nov 11, 2013 at 10:31 AM, Volker Braun wrote:
>>> On Monday, November 11, 2013 10:09:54 AM UTC-8, Ralf Hemmecke wrote:
But I think even if I send that log, the bug is rather
On Monday, November 11, 2013 11:55:56 PM UTC-8, Snark wrote:
>
> example: disabling threading in ecl
Perhaps the scope of the Sage project is different from that of an embedded
Lisp interpreter?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
T
Le 11/11/2013 20:45, Robert Bradshaw a écrit :
> On Mon, Nov 11, 2013 at 10:31 AM, Volker Braun wrote:
>> On Monday, November 11, 2013 10:09:54 AM UTC-8, Ralf Hemmecke wrote:
>>>
>>> But I think even if I send that log, the bug is rather that Sage should
>>> check "git --version" and then don't st
On 11/11/2013 07:22 PM, William Stein wrote:
>> check "git --version" and then don't start trying to build git at all,
> If this (and any other similar) change is made, it needs to be made in
> a way that doesn't mess up the binaries we build. The binaries that
> are built for generic redistribut
This is now http://trac.sagemath.org/15401 (needs review)
On Monday, November 11, 2013 1:03:29 PM UTC-8, Volker Braun wrote:
>
> This has been reported before at
> https://groups.google.com/d/msg/sage-git/4JtJ9w-kmTw/tWdXPChx4d4J
>
>>
>>
--
You received this message because you are subscribed t
>> check "git --version" and then don't start trying to build git at all,
> That is really a feature request, not a bug. Of course it would be nice. If
> you want to work on a configure-style script that queries the system for
> build- and runtime dependencies then please do!
Interesting! You
This has been reported before at
https://groups.google.com/d/msg/sage-git/4JtJ9w-kmTw/tWdXPChx4d4J
On Monday, November 11, 2013 12:04:40 PM UTC-8, Ralf Hemmecke wrote:
>
> > It would be nice if you could answer Vincent's question about the
> > full build log so it can be fixed.
>
--
You rece
> It would be nice if you could answer Vincent's question about the
> full build log so it can be fixed.
As promised...
Oh, interesting, I just looked through it. One can find there something like
/bin/sh: 1: curl-config: not found
/bin/sh: 4: autoconf: not found
/bin/sh: 1: msgfmt: not found
b
Hi,
I definitely think that aim of Felix is good and needed. For example,
it is hard to incorporate python module into Sage distribution (I
recently went into troubles with pygtk). I guess that having Sage
working with the builtin Python would solve the problem. Could
someone confirm ?
It is har
On Mon, Nov 11, 2013 at 10:31 AM, Volker Braun wrote:
> On Monday, November 11, 2013 10:09:54 AM UTC-8, Ralf Hemmecke wrote:
>>
>> But I think even if I send that log, the bug is rather that Sage should
>> check "git --version" and then don't start trying to build git at all,
>> no?
>
>
> That is
On Mon, Nov 11, 2013 at 07:09:54PM +0100, Ralf Hemmecke wrote:
> But I think even if I send that log, the bug is rather that Sage should
> check "git --version" and then don't start trying to build git at all,
> no?
"checking whether is necessary" is one part of the problem.
according to some sag
Le 11/11/2013 19:31, Volker Braun a écrit :
> On Monday, November 11, 2013 10:09:54 AM UTC-8, Ralf Hemmecke wrote:
>
> But I think even if I send that log, the bug is rather that Sage should
> check "git --version" and then don't start trying to build git at all,
> no?
>
> That is rea
On Mon, Nov 11, 2013 at 06:39:28PM +0100, Ralf Hemmecke wrote:
> Obviously your (and probably others) opinion is that a sage installation
> as approached by Felix for Debian cannot easily be lifted to other
> non-debian distributions. I haven't actually looked at any code (so I'm
> rather uninforme
On Monday, November 11, 2013 10:09:54 AM UTC-8, Ralf Hemmecke wrote:
>
> But I think even if I send that log, the bug is rather that Sage should
> check "git --version" and then don't start trying to build git at all,
> no?
>
That is really a feature request, not a bug. Of course it would be nic
On Mon, Nov 11, 2013 at 10:09 AM, Ralf Hemmecke wrote:
>>> My initial question was "What requirement for git does Sage have?"
>
>> It should have none, you found a bug. It would be nice if you could answer
>> Vincent's question about the full build log so it can be fixed.
>
> OK. I can only dig th
>> My initial question was "What requirement for git does Sage have?"
> It should have none, you found a bug. It would be nice if you could answer
> Vincent's question about the full build log so it can be fixed.
OK. I can only dig that out later.
But I think even if I send that log, the bug i
On Monday, November 11, 2013 10:00:21 AM UTC-8, Ralf Hemmecke wrote:
>
> My initial question was "What requirement for git does Sage have?"
>
It should have none, you found a bug. It would be nice if you could answer
Vincent's question about the full build log so it can be fixed.
--
You rece
>> mean that a sage installation should never install anything that is
>> already available in a standard distribution.
> Even if that means that the Sage testsuite fails because distribution
> packages have a bug that isn't fixed upstream yet? Thats an important
> policy question and we never
On Monday, November 11, 2013 9:39:28 AM UTC-8, Ralf Hemmecke wrote:
>
> Of course, I
> mean that a sage installation should never install anything that is
> already available in a standard distribution.
>
Even if that means that the Sage testsuite fails because distribution
packages have a bug
On 11/11/2013 06:29 PM, Volker Braun wrote:
> Its not a technical problem - I think Felix is technically very competent.
> But he didn't listen to our concerns nor did he engage in discussions. He
> continues to be focused on Debian whereas Sage has a much larger target. In
> the end, a Debian
On Monday, November 11, 2013 7:51:23 AM UTC-8, Snark wrote:
>
> Can we get the un-sarcastic direct criticism to discuss on technical
> merit?
>
Its not a technical problem - I think Felix is technically very competent.
But he didn't listen to our concerns nor did he engage in discussions. He
c
Le 11/11/2013 16:25, Volker Braun a écrit :
> On Monday, November 11, 2013 7:11:20 AM UTC-8, Felix Salfelder wrote:
>
> > Fixed that for you.
>
> that's great. would you be so kind and tell me/us where to find it and
> how to make use of it?
>
> FTFY (Often used sarcastically) - no
On Monday, November 11, 2013 7:11:20 AM UTC-8, Felix Salfelder wrote:
>
> > Fixed that for you.
>
> that's great. would you be so kind and tell me/us where to find it and
> how to make use of it?
FTFY (Often used sarcastically) - not to fix an honest mistake, but to
sarcastically disagree wi
On Mon, Nov 11, 2013 at 06:53:37AM -0800, Volker Braun wrote:
> On Sunday, November 10, 2013 10:14:30 AM UTC-8, Felix Salfelder wrote:
> >
> > the idea is to run sage (the distribution) on top of debian. and
> > only compile packages that deviate from upstream or the debian
> > package.
>
>
> F
On Sunday, November 10, 2013 10:14:30 AM UTC-8, Felix Salfelder wrote:
>
> the idea is to run sage (the distribution) on top of debian. and
> only compile packages that deviate from upstream or the debian
> package.
Fixed that for you.
--
You received this message because you are subscribed
On Sun, Nov 10, 2013 at 01:02:30PM -0500, Vincent Delecroix wrote:
> I do really think that this is the best of what can
> happen for Sage but I also think that we need an agreement of all Sage
> developers that spkg can not be patched...
actually, it's the other way around. if there were no patc
2013/11/10, Felix Salfelder :
> On Sun, Nov 10, 2013 at 04:56:58PM +0100, Ralf Hemmecke wrote:
>> What actually surprises me is that Sage must build git at all. Wouldn't
>> it make sense to restrict build and development scripts to use features
>> of a git version number that is usually satisfied b
> The part of the log you paste is not long enough. I guess you need to
> install msgfmt which is not part of standard debain. The name of the
> package is gettext.
Thanks. I'd probably found that myself. But of course, that was not my
point.
> Does anybody know why git is a standard spkg ? It is
On Sun, Nov 10, 2013 at 04:56:58PM +0100, Ralf Hemmecke wrote:
> What actually surprises me is that Sage must build git at all. Wouldn't
> it make sense to restrict build and development scripts to use features
> of a git version number that is usually satisfied by current major
> stable distributi
Hi,
The part of the log you paste is not long enough. I guess you need to
install msgfmt which is not part of standard debain. The name of the
package is gettext.
Does anybody know why git is a standard spkg ? It is likely that
anybody has his/her own git...
Vincent
2013/11/10, Ralf Hemmecke :
37 matches
Mail list logo
