public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <warren@etr-usa.com>
To: Cygwin Apps List <cygwin-apps@cygwin.com>
Subject: Package categorization inconsistencies
Date: Wed, 22 Jan 2014 02:03:00 -0000	[thread overview]
Message-ID: <52DF2707.7050809@etr-usa.com> (raw)

While doing my "how big is a full Cygwin installation" research[*], I 
came across some inconsistencies in package categorization:


perl_debuginfo: Not in the Debug category.  It is also the only package 
named *_debuginfo instead of *-debuginfo

cdrkit-doc, fftw33-doc, flac-docs, gsl-doc, gtk-doc,
ImageMagick-doc, libcaca-doc, libcloog-isl-doc, libdatrie-doc,
libgmp-doc, libgstreamer1.0-doc, libisl-doc, liblapack-doc,
libmpc-doc, libmpfr-doc, libpoco-doc, libsigc2.0-doc, libthai-doc,
libunistring-doc, libxcb-doc, libxml2-doc, libxslt-doc, libxslt2-doc,
llvm-doc, octave-doc, postgresql-doc, ppl-doc, qt4-doc, ruby-doc,
texlive-collection-*-doc, tiff-doc: Not in Doc category

The Doc category seems to have two different purposes: documentation, 
and tools to create documentation.  Currently, there are far more of the 
former in this category.  Should there be a new category for the tools? 
  (e.g. gnome-doc-utils, man, manlint, pinfo, xmlto...)

glproto, presentproto, xextproto, xproto: In Devel category, but not X11 
category, yet they are part of X11.  And, vice versa: the other *proto 
packages that are in X11 probably should be in Devel, too.


[*] http://goo.gl/lu61sZ

             reply	other threads:[~2014-01-22  2:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22  2:03 Warren Young [this message]
2014-01-24  9:32 ` Corinna Vinschen
2014-01-24 22:10   ` Warren Young

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

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

  git send-email \
    --in-reply-to=52DF2707.7050809@etr-usa.com \
    --to=warren@etr-usa.com \
    --cc=cygwin-apps@cygwin.com \
    /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.
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).