On 09/01/2016 05:39 PM, François Bissey wrote:
>
> Let's talk about practical matters. I have giacpy_sage in the
> sage-on-gentoo overlay already. How would you suggest to deal with this,
> in this context?
>
Since there's no API/ABI convention for the sage library, you have to
rebuild giacpy_
On 2016-09-01, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> We should not forbid inheriting from SageObect/Element,
> Parent/CategoryObject in external packages. We should just provide a
> simple way to automatize the recompilation. This is a step toward
> modularization.
Totally +1!
On 02/09/16 01:51, Michael Orlitzky wrote:
On 09/01/2016 09:46 AM, leif wrote:
Exactly. (See also my other reply.)
It would be dumb and totally annoying if all such packages would get
rebuilt upon *any* change to the Sage library, and just as bad as having
to "manually" figure out /which/ pac
On 09/01/2016 09:46 AM, leif wrote:
>
> Exactly. (See also my other reply.)
>
> It would be dumb and totally annoying if all such packages would get
> rebuilt upon *any* change to the Sage library, and just as bad as having
> to "manually" figure out /which/ packages might need rebuilding after
Vincent Delecroix wrote:
> On 01/09/16 04:34, Jeroen Demeyer wrote:
>> On 2016-08-31 23:26, Vincent Delecroix wrote:
>>> Hello,
>>>
>>> In the optional package giacpy there are some extension classes that
>>> depend on SageObject.
>>
>> Does it really only need SageObject? I see no reason why giacp
Vincent Delecroix wrote:
> On 31/08/16 19:48, leif wrote:
>> leif wrote:
>>> leif wrote:
Vincent Delecroix wrote:
> Hello,
>
> In the optional package giacpy there are some extension classes that
> depend on SageObject. Hence if I do some modification to SageObject
> and
>>
On 31/08/16 19:48, leif wrote:
leif wrote:
leif wrote:
Vincent Delecroix wrote:
Hello,
In the optional package giacpy there are some extension classes that
depend on SageObject. Hence if I do some modification to SageObject and
perform "make" the giacpy package is broken. Is there a solution
leif wrote:
> leif wrote:
>> leif wrote:
>>> Vincent Delecroix wrote:
Hello,
In the optional package giacpy there are some extension classes that
depend on SageObject. Hence if I do some modification to SageObject and
perform "make" the giacpy package is broken. Is there a
leif wrote:
> leif wrote:
>> Vincent Delecroix wrote:
>>> Hello,
>>>
>>> In the optional package giacpy there are some extension classes that
>>> depend on SageObject. Hence if I do some modification to SageObject and
>>> perform "make" the giacpy package is broken. Is there a solution to
>>> rebui
leif wrote:
> Vincent Delecroix wrote:
>> Hello,
>>
>> In the optional package giacpy there are some extension classes that
>> depend on SageObject. Hence if I do some modification to SageObject and
>> perform "make" the giacpy package is broken. Is there a solution to
>> rebuild external packages
Vincent Delecroix wrote:
> Hello,
>
> In the optional package giacpy there are some extension classes that
> depend on SageObject. Hence if I do some modification to SageObject and
> perform "make" the giacpy package is broken. Is there a solution to
> rebuild external packages that depends on sag
11 matches
Mail list logo
