It's worth mentioning that the errno utility has also moved out of ubuntu-dev-tools, at the strong request of the maintainer of ubuntu-dev-tools. I tried (in vain) to get errno into various other packages and upstream projects, and failed in all cases. As of Natty, you can:
For older releases:
As a reminder, you can use errno in these ways:
$ errno font
EBFONT 59 /* Bad font file format */
$ errno 36
ENAMETOOLONG 36 /* File name too long */
$ errno EPERM
EPERM 1 /* Operation not permitted */
You can find the sources with:
And the launchpad project is at http://launchpad.net/errno.
Similarly, the maintainer of the openssh package in Ubuntu urged the removal of the ssh-import-id utility. Once again, I offered the tool to the upstream openssh project, to no avail. So ssh-import-id now lives in its own source and binary packages. As of Natty, you can:
For older releases:
As a reminder, you can use ssh-import-id in this way:
INFO: Successfully authorized [kirkland]
INFO: Successfully authorized [smoser]
You can find sources with:
And the launchpad project is at http://launchpad.net/ssh-import-id.
"So why didn't you just use bikeshed?" Great question! When I showed run-one to one of my colleagues, he said, "Neat, I'd use that, where can I get it?" And I pointed him to install bikeshed, to which he responded, "Oh, well, I just want run-one, but not all the other cruft you put into bikeshed." :-)
I tried not to be offended, but in the end, he was right. I thought about splitting bikeshed into a series of bikeshed-$FOO binary packages. This wasn't ideal, though, in my opinion, from the perspective of developing code or handling bugs/questions.
Thus, I've decided to create a new Launchpad project and team, and Ubuntu package for each of these stand-alone utilities.
I'll continue to use bikeshed to incubate new tools, and as soon as they're ready to stand alone, then I'll split them out to their own branch/project/team/package.