Comment 13 for bug 385098

I'm glad you appreciate it Chris, it was fun to write it!

[2]

+ update-motd | lsb-base (<< 3.2-14ubuntu2),

This is indeed a tricky and hacky bit. I thought about Recommend as
well, but I find the motd feature very cool and I'd like to make it
very sure that we have it all the time, hence the Depend (although you
are right a Recommend would realistically do the job in most cases).

Now about "| lsb-base (<< 3.2-14ubuntu2)", that basically says "Oh,
and if you don't have update-motd because you are running hardy or
dapper, just don't bother". What happens is that if you are on hardy
or intrepid APT won't find update-modt, and will consider lsb-base <<
3.2-14ubuntu2, which is satisfiable on hardy and dapper. If instead
are on >= intrepid, then "lsb-base (<< 3.2-14ubuntu2)" can't be
satisfied, and APT will be forced to install update-motd. I picked
lsb-base because it doesn't add anything unnecessary, as it is a
package with priority "required", and it will be present in any
installation (it installed by default by debootstrap).

Note also that in landscape-common.postinst we run:

           /usr/sbin/update-motd 2>/dev/null || true

which is safe, in case update-motd isn't there.

[3]
+ python-smartpm | smartpm-core (>= 1.1),

Yeah, we could get rid of it indeed. I just left it because our
smartpm 1.1 packages are actually enough for landscape-1.3.2, is if
somebody doesn't want to upgrade it for some reason, it's still
fine. However I've built smart 1.2 for all our target releases (that's
in my PPA as well), and the plan is indeed to replace the smart 1.1
package in your <= repositories with it.