public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stewart Honsberger <blkdeath@gentoo.org>
To: gentoo-dev@gentoo.org
Cc: gentoo-core@gentoo.org
Subject: [gentoo-dev] Portage, SLOT, functionality, documentation, ChangeLog
Date: Sat, 12 Jul 2003 15:01:33 -0400	[thread overview]
Message-ID: <3F105B0D.8050200@gentoo.org> (raw)

I've talked about this several times, but I wanted to get it out in the 
open;

Portage has an abhorrent lack of documentation, I'd like to see that 
changed. Possibly
(especially) before a 1.4 release.

There are dozens upon dozens of facets of key functionality that are 
simply not
explained, or not clearly explained. If they are, they're given a 
sentence here and there,
scattered all about the Gentoo website, man/info pages, CVS, etc.

Also, and I can't stress this enough, a ChangeLog is *required*. When 
key functionality
is introduced, updated, removed, or significantly altered, it is 
imperative that users
and developers alike can be easily appraised of it in a common location.

A roadmap would also help a lot of people rest easy at night. Whether it 
is the case or
not, it seems as if major changes take place in Portage on a whim. If 
they are planned,
the general userbase has no foreknowledge of said plans and these 
changes come as
a complete surprise when finally marked stable in the tree (if people 
even know they
exist, due to the aforementioned lack of documentation).

Thoughts? Ideas?

-- 
Stewart Honsberger
http://blackdeath.snerk.org/
"Capitalists, by nature, organize to protect themselves.
-- Geeks, by nature, resist organizaion."


--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-07-12 19:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-12 19:01 Stewart Honsberger [this message]
2003-07-12 19:39 ` [gentoo-dev] Portage, SLOT, functionality, documentation, ChangeLog Grant Goodyear
2003-07-13 20:39 ` [gentoo-dev] Re: [gentoo-core] " Nick Jones
2003-07-13 23:07   ` Mike Frysinger
2003-07-14 17:52   ` Stewart Honsberger

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=3F105B0D.8050200@gentoo.org \
    --to=blkdeath@gentoo.org \
    --cc=gentoo-core@gentoo.org \
    --cc=gentoo-dev@gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox