On Tuesday, 26 January 2016 20:40:07 UTC, Volker Braun wrote:
>
> I created http://trac.sagemath.org/ticket/19967 for dealing with cliquer
>
ready for review, by the way...
>
>
> On Tuesday, January 26, 2016 at 3:36:24 PM UTC-5, Volker Braun wrote:
>>
>> For the record, the OSX binaries are br
On Wed, Jan 27, 2016 at 12:55 AM, Jeroen Demeyer wrote:
> On 2016-01-26 17:08, William Stein wrote:
>>
>> He said that only dead code in maintenance only mode
>> should be added, etc., etc.
>
>
> So we can never add new features to Python? That's depressing...
Heh, I'm just reporting what he said
On 2016-01-26 17:08, William Stein wrote:
He said that only dead code in maintenance only mode
should be added, etc., etc.
So we can never add new features to Python? That's depressing...
I'm
actually really shocked that in all the discussion about getting
packages into Sage, we fixed on voti
I created http://trac.sagemath.org/ticket/19967 for dealing with cliquer
On Tuesday, January 26, 2016 at 3:36:24 PM UTC-5, Volker Braun wrote:
>
> For the record, the OSX binaries are broken because cliquer fails to
> install; the log contains:
>
> error:
> /Applications/Xcode.app/Contents/Deve
For the record, the OSX binaries are broken because cliquer fails to
install; the log contains:
error:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool:
changing install names or rpaths can't be redone for:
/Users/vbraun/Code/binary-pkg/
On Tue, Jan 26, 2016 at 10:36 AM, Nathann Cohen wrote:
>> Nathann:
>
> William,
>
> I'm sorry to say that the situation [...]
I have over the years seen dozens of incredible Sage developers who
could do what we are talking about, but have to instead work fulltime
industry jobs now since open sou
> Nathann:
William,
I'm sorry to say that the situation is not as simple as "You suggest,
and you are happy to see people doing it for you".
Sometimes, people do stuff because nobody would do it otherwise. They
feel responsible as members of the community, and so give it a try. I
swear: trust me
Nathann:
> I can't help but notice that you say "we" when you say what should be
done, and you say "you" when there is actual work ahead.Will you
help? Or will you wait for Sage developers to do it?
It occurred to me that another reason I've been doing this is because
it gives me a sense for
> Wouldn't be possible to make a cliquer package ?
There is one already, installed in Sage by default.
This package is a copy of the cliquer tarball that you can download
from its official website. It contains a 'minimal' build system, which
does not work on all platforms that Sage supports. For
Wouldn't be possible to make a cliquer package ?
Le 26/01/2016 18:20, William Stein a écrit :
On Tue, Jan 26, 2016 at 9:02 AM, Nathann Cohen wrote:
contributions. E.g., they won't even consider a new component be
added to Python unless somebody clearly commits to supporting the
contribution
On Tue, Jan 26, 2016 at 9:42 AM, Nathann Cohen wrote:
>>> Are you one of them?
>>
>> Rolls eyes...
>
> I can't help but notice that you say "we" when you say what should be
> done, and you say "you" when there is actual work ahead.
I am too busy to work on core Sage development right now. If wh
>> Are you one of them?
>
> Rolls eyes...
I can't help but notice that you say "we" when you say what should be
done, and you say "you" when there is actual work ahead.
You reported this problem concerning cliquer, and you are "all for
Sage developpers contributing upstream". Will you help?
Or w
On Tue, Jan 26, 2016 at 9:35 AM, Nathann Cohen wrote:
>> Hey I was just reporting on a conversation with Guido about what they
>> *already* do with Python.
>
> It ended with "we should do the same in Sage"
I was talking about packages not code.
>> Huge +1. I'm all for Sage devs contributing ups
> Hey I was just reporting on a conversation with Guido about what they
> *already* do with Python.
It ended with "we should do the same in Sage"
> Huge +1. I'm all for Sage devs contributing upstream :-)
Are you one of them?
Nathann
--
You received this message because you are subscribed to
On Tue, Jan 26, 2016 at 9:02 AM, Nathann Cohen wrote:
>> contributions. E.g., they won't even consider a new component be
>> added to Python unless somebody clearly commits to supporting the
>> contribution for "five years". And of course the people making that
>> commitment have to be reputable
>
> contributions. E.g., they won't even consider a new component be
> added to Python unless somebody clearly commits to supporting the
> contribution for "five years". And of course the people making that
> commitment have to be reputable.We should do the same for Sage --
>
Don't you
On Tue, Jan 26, 2016 at 7:59 AM, Volker Braun wrote:
> The cliquer "buildsystem" is a steaming pile of s**t, it clearly should not
> be a standard package. For starters, it shouldn't install a .so on darwin...
Agreed. In fact, here's a (was private) email I wrote in 2009 after
having lunch with G
17 matches
Mail list logo
