unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: trentbuck@gmail.com (Trent W. Buck)
To: emacs-devel@gnu.org
Subject: Re: List packages Status column terminology
Date: Fri, 24 Jan 2014 10:38:59 +1100	[thread overview]
Message-ID: <87sisemfos.fsf@gmail.com> (raw)
In-Reply-To: jwv8uuen1cj.fsf-monnier+emacs@gnu.org

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> "available" is not a great choice, tho.  The suggested "not installed"
> might be a bit better, but it's longer and I'd rather try and shorten
> this column.
>
> Any other idea?

For comparison, aptitude uses these terms:

  Upgradable Packages (71)
    A newer version of these packages is available.

  New Packages (82)
    These packages have been added to Debian since the last time you
    cleared the list of "new" packages (choose "Forget new packages"
    from the Actions menu to empty this list).

  Installed Packages (746)
    These packages are currently installed on your computer.

  Not Installed Packages (41034)
    These packages are not installed on your computer.

  Obsolete and Locally Created Packages (6)
    These packages are currently installed on your computer, but they
    are not available from any apt source.  They may be obsolete and
    removed from the archive, or you may have built a private version of
    them yourself.

  Virtual Packages (5748)
    These packages do not exist; they are names other packages use to
    require or provide some functionality.

They appear horizontally as grouping elements in a tree view,
so they use up one line each instead of umpteen columns.

Each package also has one to four single-letter codes in a generic
"status" column, "i" for installed, "A" for automatically installed by
something else, "p" for not installed, "v" for virtual, etc.  They
mostly correspond to the dpkg codes,

    Desired=Unknown/Install/Remove/Purge/Hold
    | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
    |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
    ||/   Name    Vers  Description
    xyz   hello   1.0   The classic greeting, and a good example




  parent reply	other threads:[~2014-01-23 23:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17  4:56 List packages Status column terminology Sivaram Neelakantan
2014-01-17  8:53 ` Thien-Thi Nguyen
2014-01-17 10:19   ` Bozhidar Batsov
2014-01-17 14:17 ` Stefan Monnier
2014-01-17 14:35   ` David Kastrup
2014-01-17 15:12     ` Vibhav Pant
2014-01-17 15:57   ` Drew Adams
2014-01-17 16:15     ` Vibhav Pant
2014-01-17 17:39       ` Drew Adams
2014-01-17 17:54   ` Sivaram Neelakantan
2014-01-17 21:28     ` Stefan Monnier
2014-01-17 22:55       ` Bozhidar Batsov
2014-01-18  2:44       ` Sivaram Neelakantan
2014-01-19  1:57         ` Stefan Monnier
2014-01-18 12:33   ` Richard Stallman
2014-01-18 12:55     ` Sivaram Neelakantan
2014-01-23 23:38   ` Trent W. Buck [this message]
2014-01-24 16:07     ` Stefan Monnier
2014-01-25  1:32       ` Trent W. Buck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sisemfos.fsf@gmail.com \
    --to=trentbuck@gmail.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).