Hi Timo.

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?

> As soon as this works, then it would be possible to use this to generate 
> debian packages, since portage keeps track of installed binary files for 
> packages. So the debian/rules file could query portage for which files 
> should go into which binary package.

the goal of the/my gsoc project would be streamlining the packaging of
debian/gentoo/whatever packaging process. having to use an extra layer
("portage"), makes things worse. no debian maintainer i can think of
would seriously use it.

> The only technical obtacle I can think of is that you'll likely want to 
> eventually install the sage tree somewhere under /usr/lib/sage, or 
> /opt/sage or something. So portage should compile for that prefix. But it 
> should "install" under debian/tmp. That should be possible, especially 
> since portage uses its own DESTDIR too.

any sane build system understands --prefix and DESTDIR, also the ones
i'm proposing to write. (but install paths is not everything.)

how about talking about build systems for the sage modules that suit
all, including sage ("the distribution") gentoo and debian? you could
help explain to sage developers, why modularization and build systems
are inevitable...

regards
felix

PS: i don't want to make your work obsolete, but it's obviously too
gentoo centric

-- 
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.


Reply via email to