From: Grant Goodyear <g2boojum@gentoo.org>
To: Stewart Honsberger <blkdeath@gentoo.org>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Portage, SLOT, functionality, documentation, ChangeLog
Date: 12 Jul 2003 15:39:45 -0400 [thread overview]
Message-ID: <1058038785.3216.32.camel@localhost> (raw)
In-Reply-To: <3F105B0D.8050200@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1863 bytes --]
> Portage has an abhorrent lack of documentation, I'd like to see that
> changed. Possibly
> (especially) before a 1.4 release.
I don't think there's a snowball's chance in Death Valley of that
happening, just due to time restrictions. It's certainly true, though,
that we do need to consolidate and improve the portage docs.
> 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.
You'll find that the ChangeLog gets installed in
/usr/share/doc/portage-x.y.z. Of course, it might be nice to know
what's changed before you upgrade. The ChangeLog in sys-apps/portage
incorrectly points people to viewcvs on cvs.g.o, although that's simple
enough to fix. Slightly more difficult is the fact that gentoo-src is
no longer linked to viewcvs. Since portage and rc scripts are developed
there, having web access is really handy. Can we fix that? (Numerous
cheers, by the way, for the prompt return of viewcvs. Thanks!!!)
> 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).
*Grin* The roadmap _used_ to be a "TODO" block in portage.py. Having a
somewhat more formal roadmap would be a nice idea, and I don't know if
one exists or not, although I'd be rather surprised if one didn't.
Best,
g2boojum
--
Grant Goodyear <g2boojum@gentoo.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-12 19: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 [this message]
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=1058038785.3216.32.camel@localhost \
--to=g2boojum@gentoo.org \
--cc=blkdeath@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