Hi Julian On Mon, Apr 22, 2013 at 01:24:21PM +0200, Julian Rüth wrote: > * Felix Salfelder <fe...@salfelder.org> [2013-04-22 13:01:20 +0200]: > > On Mon, Apr 22, 2013 at 03:15:54AM -0700, Timo Kluck wrote: > > > We're trying to replace the current spkg system (actually the spkg system > > > like it exists in the git repo) by some version of Gentoo's portage. This > > > would be similar to the lmonade project, except that it's trying to be a > > > smooth transition from the current source distribution. > > are you targeting sage-upstream or is this a local hack that is doomed > > to fail some releases (and several git-transitions) later? > We're targeting sage/git upstream.
is this planned to be part of sage? then i'd suspect you are trying to rewrite sage "the distribution". would it help to have build-systems for the (non foreign) parts of sage? > You don't have to use portage. If all spkgs are debian packages, then > there is no point in using portage since you won't be using any spkgs > anyway. You could of course use it as part of the build process and > unmerge portage in a final step to remove it again. packaging into .deb instead of .spkg as in my first proposal does the trick (for debian), as long as sage uses spkgs. a distribution friendly build system for some, including libcsage/sage-python is missing nevertheless. have you written one? > I don't believe it is gentoo centric. Actually, I'm not even using > gentoo myself anymore. > The current SPKG approach has its problems, especially with the new git > layout. One main problem being that you cannot uninstall an SPKG when > you switch to a branch where it is not present. That's where we want to > use portage. I at least don't think of portage here as a distribution > system, but just as a tool to configure/install/uninstall things in a > local prefix. debian has already packages for most of the foreign packages, and this is totally unrelated to sage. what i need is just packages for the core modules (currently the directories in <git-transition>/src). my proposal is to handle all modules (foreign or not) alike, and add build systems where missing -- so packages can also be built for debian, gentoo, whatever-you-like. but i'm interested in how you handle it! regards felix -- 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.
