[Pkg-ltsp-devel] code comparison of branches

[vagrant at freegeek.org]

i looked over otavio's "for-merge-fixes" branch, and made a few patches to
fix some things that didn't seem to merge well, and add some features that
didn't seem to get merged in at all.
http://llama.freegeek.org/~vagrant/bzr-archives/ltsp/for-merge-fixes/

i noticed a few other things that were different between my debianfixes
and ubuntufixes branch and the for-merge branch:
subprocess.py needs to be included with ldm to work on sarge.

ltsp-build-client.conf is not included. i don't know if we want to change
that. many of the values have defaults in ltsp-build-client itself. some
of them make sense there, but might make more sense to only include in a
configuration file. i tend to feel that maybe we should make extensive use
of commandline options, and ditch the configuration file, but include a
commandline option to include a custom configuration file.
ed and nvi were excluded from the debootstrap chroot in the debianfixes
branch, presumably to save some space, but are not excluded in the
for-merge branch.
the debianfixes branch also has support for using debootstrap's
dependency resolution- i don't know how important it is to include that
feature.
there's also a feature in debianfixes to disable sshd, which saves a bit
of ram, though should probably be made optional.
also in debianfixes, ltsp-build-client removes /var/log/ksymoops. this can
save a *lot* of ram when /var/log is mounted in tmpfs/unionfs, and i've
never seen bad effects from removing the directory. i don't really
understand what it does, though.
there also isn't really a need to warn about the entry in /opt/exports in
the package postinst, as it is handled in ltsp-build-client now (though
i'd like to see it properly handle when ROOT != /opt/ltsp/$ARCH).
i don't know how we want to handle sarge-backport specific stuff. it would
be nice if we didn't have to build separate packages just to do a trivial
backport.  in many ways, i'd prefer to do development on sarge, as it's
less of a moving target than etch or ubuntu releases. so my primary
interest in the ltsp packages is for sarge backports.
i'll try and build packages and do some tests with qemu tomorrow.

live well,
  vagrant