From: Nick Jones <carpaski@gentoo.org>
To: Stewart Honsberger <blkdeath@gentoo.org>
Cc: gentoo-dev@gentoo.org, gentoo-core@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-core] Portage, SLOT, functionality, documentation, ChangeLog
Date: Sun, 13 Jul 2003 20:39:33 +0000 [thread overview]
Message-ID: <20030713203933.GA5851@twobit.net> (raw)
In-Reply-To: <3F105B0D.8050200@gentoo.org>
> Portage has an abhorrent lack of documentation, I'd like to see
> that changed. Possibly (especially) before a 1.4 release.
This is mentioned every once in a while, but to 'see that changed'
really does not help. SpanKY and a few other (greatly appreciated
individuals) make great contributions towards documenting all the
little bits that are missing, but, as you note, there is a lot that
needs to be worked out. Time and I are not great friends, but I try
to keep up with what I make changes to (albeit most are only noted
in the changelog, make.conf, and emerge --help).
Care to help?
> 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).
Well... It's not on a whim... But I'll be working on improving
(read: creating) the public project plan/roadmap... as most of
it is my written notes and bugs.gentoo.org.
--NJ
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-13 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 19:01 [gentoo-dev] Portage, SLOT, functionality, documentation, ChangeLog Stewart Honsberger
2003-07-12 19:39 ` Grant Goodyear
2003-07-13 20:39 ` Nick Jones [this message]
2003-07-13 23:07 ` [gentoo-dev] Re: [gentoo-core] " 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=20030713203933.GA5851@twobit.net \
--to=carpaski@gentoo.org \
--cc=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