commandlinefu.com is the place to record those command-line gems that you return to again and again.
Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/
You can sign-in using OpenID credentials, or register a traditional username and password.
First-time OpenID users will be automatically assigned a username which can be changed after signing in.
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
Find when debian packages were installed on a system.
There are 2 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
nice companion to dpkg --get-selections ! +1
How would you join that with dpkg --get-selections ! +1 ?
You can use --get-selections and --set-selections to save and restore the set of packages you have installed so that you don't have to remember every minor package name, like in a fresh reinstall and you don't remember the name of all those latex packages you installed months/years ago.
.
But their is no distinguishing between what the user wanted and what was also automatically installed because it was a dependency. At least with /var/lib/dpkg/info the .list files have timestamps, so you can see the packages sorted into groups by time and (in some rough order) by dependency.
there's also the combination of apt-history and metche... or so I've heard and lightly tested