destabilizing changes such as rxgk and pthreaded bos land on master to
settle.
-A 1.8 release would also bring the possibility of using shared libraries,
+A 1.8 release would also bring the possibility of using shared libraries,
which are now available with the use of libtool. Currently (on master),
all executable binaries are still linked mostly statically, and most of
the shared libraries that are produced during the build are not installed
is created.
Things to be done pre-branching (aka before pre1):
-
+
* [done] Make roken, hcrypto, and kopenafs use libtool to build
* [done] Make sure libtool is used properly elsewhere, in particular to install
shared versions of libafsrpc and libafsauthent, which we ship in
authenticated connections to the VL server.
Things to be removed from 1.8 post-branch:
-
+
* `src/rxgk`; it is not going to be usable in 1.8
* `src/mcas`; it is not going to be usable in 1.8
Things to be removed from master post-branch:
-
+
* Several `tfoo` can probably be moved to just `foo`; things like
`tptserver`, `tvlserver`, `tvolser`, `tsalvaged`. I'm not sure whether
`tbudb` and/or `tbutc` are ready.
* push to empty out libutil as much as possible.
-* rip out LWP support
-* it is tempting to remove kauth, but probably not possible due to agreements with IBM.
+* convert xstat et all from LWP to pthread
+* rip out LWP support (move to kauth?)
+* it is tempting to remove kauth, but probably not possible due to agreements with IBM., move to historical?
* `make dest` support? Pretty-please?
-* upserver
+* upserver ? Note: This is still in use at numerous sites, so is not currently a good candidate for removal
* non-DA fileserver and associated bitmap-later and fast-restart configure knobs
-* inode fileserver?
+* inode fileserver? and src/fsck
+
+Other candidates for removal:
+
+* src/afsinstall
+* src/afsweb
+* src/JAVA and TechNotes-JavaAPI
git://git.openafs.org / openafs-wiki.git / blobdiff