summaryrefslogtreecommitdiff
path: root/pkgtools
diff options
context:
space:
mode:
authordmcmahill <dmcmahill@pkgsrc.org>2001-04-28 13:49:43 +0000
committerdmcmahill <dmcmahill@pkgsrc.org>2001-04-28 13:49:43 +0000
commit03bda0fd9e6aea3aaf77611612248bea731db5bb (patch)
tree7601bc5a342f9ed596b599680a735baad19ccc9a /pkgtools
parent7d651a26224ff128919ce781d0d87b4f6b3ad6de (diff)
downloadpkgsrc-03bda0fd9e6aea3aaf77611612248bea731db5bb.tar.gz
add a TODO/wish list. This file is only there to be read by someone who
wants to hack on the package and is not otherwise used (so I don't feel bad adding it during the freeze).
Diffstat (limited to 'pkgtools')
-rw-r--r--pkgtools/cdpack/files/TODO20
1 files changed, 20 insertions, 0 deletions
diff --git a/pkgtools/cdpack/files/TODO b/pkgtools/cdpack/files/TODO
new file mode 100644
index 00000000000..17b1a0bcde7
--- /dev/null
+++ b/pkgtools/cdpack/files/TODO
@@ -0,0 +1,20 @@
+$NetBSD: TODO,v 1.1 2001/04/28 13:49:43 dmcmahill Exp $
+
+To-Do List for cdpack
+---------------------
+
+
+- extract COMMENT and DESCR to generate a browseable index of all the
+ packages on the CD set. This would be similar to the README.html's
+ in pkgsrc, but with some modifications. The changes would be to
+ list which CD certain pkgs are on. Also, if a DEPENDS is not on the
+ CD set (due to redistribution restrictions for example), perhaps
+ list that so the user knows s/he must install the restricted DEPENDS
+ by hand first.
+
+- come up with some sort of install tool around pkg_add. Perhaps this
+ could be done using SUSHI. The idea would be to let the user browse
+ the selection of packages, select some subset of them and then do
+ a batch install.
+
+