Update `TODO'.

This commit is contained in:
Ludovic Courtès 2013-06-14 17:05:49 +02:00
parent 16357e8c71
commit 3e5980de47
1 changed files with 11 additions and 7 deletions

18
TODO
View File

@ -41,8 +41,10 @@ Like scripts/build-remote.pl in Nix.
* user interface * user interface
** Add a package.el (Emacs) back-end ** Add a package.el (Emacs) back-end
Unfortunately package.el is monolithic, so most likely wed have to package.el is quite monolithic, but we may be able to reuse/extend
write a new one based on it, as opposed to actually using it. package-menu-mode or at least tabulated-list-mode.
** add guile-ncurses interface
* extend <origin> * extend <origin>
** add OpenPGP signatures: ** add OpenPGP signatures:
@ -82,6 +84,11 @@ create a new dir.
("i3" ,p3))) ("i3" ,p3)))
#+END_SRC #+END_SRC
* add make-sha256-port binding for gcry_md_write & co.
This should make `derivation-hash' faster.
* synchronize package descriptions with GSRC and/or the [[http://directory.fsf.org][FSD]] * synchronize package descriptions with GSRC and/or the [[http://directory.fsf.org][FSD]]
Meta-data for GNU packages, including descriptions and synopses, can be Meta-data for GNU packages, including descriptions and synopses, can be
@ -89,11 +96,8 @@ dumped from the FSD:
http://directory.fsf.org/wiki?title=GNU/Export&action=purge . http://directory.fsf.org/wiki?title=GNU/Export&action=purge .
We could periodically synchronize with that. We could periodically synchronize with that.
* support cross-compilation See http://lists.gnu.org/archive/html/bug-guix/2013-04/msg00120.html for info
on how to synchronize with GSRC's descriptions.
Implement package-cross-derivation, and add the corresponding code in
gnu-build-system. Then, actually bootstrap a cross-compilation
environmente.g., a cross-GNU environment.
* add a guildhall build system * add a guildhall build system