On 09.04.2013 10:26, Tobias Hansen wrote:
> Hi Felix,
>
> On 04/09/2013 09:49 AM, Felix Salfelder wrote:
>> a proper build system for sage ("the library") with the usual dependency
>> checks seems neccesary (if not sufficient) for distributions. i can
>> think of
>> a way to implement this (probably using autotools) and put it into a
>> debian package. such a build system won't yet get me much closer to the
>> project deliverable "support for choosing a set of dependencies within
>> sage" without messing a lot with sage ("the operating system").
>>
>> a build system for sage ("the library") could be used to switch between
>> system headers/libraries and stuff installed to /some/sage/prefix.
>> in order to make use of these switches from sage ("the operating
>> system"), the toplevel install script must be able process switches like
>> --with-ntl=/usr/include to pass to the spkg compilation, which in turn
>> means *all* spkgs must understand such flags (doesn't it?).
>
> No, the toplevel install script must just be able to skip the
> compilation of these spkg's. And tell the Sage library to use the
> libraries that are available and were compiled independently.
>
>> it seems to be more work to fix sage ("the operating sytstem") than to
>> properly ship sage ("the library") within an already working
>> distribution (= properly checking for functionality/applied patches).
>> these checks however are difficult to maintain, if upstream sage doesn't
>> use them...
>
> We want to do the changes to the build system in Sage, the two Sage
> developers agreed to keep an eye on the progress so that we end up with
> something they can accept in the end. As much tests as possible would be
> great, but how would you check for applied patches in an universal way?
> Every distribution has its own way to organize patches. I think Sage
> already has a good test coverage and a Debian package should of course
> run all the tests during build.
>
>>
>> to me, these problems (fixing sage vs. distributing sage library) seem
>> independent enough to have two GSoC projects. i have a rough idea of
>> what gentoo-prefix is doing and of Julien's pruner script, but i don't
>> see a solution there. what is your favourite way out?
>>
>> regards
>> felix
> It seems to me that you understood that Sage should build all spkg's in
> any case and just install them somewhere else. I think that means the
> step you call "fix Sage the operating system" is not needed right? Now
> that I have clarified this, any new thoughts?
>
> Cheers,
> Tobias
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
