From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] RFC: slight deunofficialisation of Unofficial Gentoo Development Guide
Date: Sun, 22 May 2005 09:35:42 +0100 [thread overview]
Message-ID: <20050522093542.2f5dfda2@snowdrop> (raw)
[-- Attachment #1: Type: text/plain, Size: 2930 bytes --]
I'd like to move the Unofficial Gentoo Development Guide [1] onto my
devspace [2]. This could be construed as weakening its unofficial status
(despite the title and the footers), so I'm asking for comments first
rather than simply doing it.
Infra -- this is about three megs of static content. I very much doubt
that this will cause any noticeable disc or bandwidth load.
If anyone objects, just reply to this email (on or off list) saying so.
No need to provide a reason, I'm not going to discuss it or ask for an
explanation -- I'll simply withdraw this request. Similarly, if anyone
wants me to stop talking about an unofficial doc on official mailing
lists, say so and I'll shut up. Finally, if anyone would like any or all
of the guide removed, just give the word.
Since I'm wasting your bandwidth anyway... Brief summary of updates
which may be of interest to some:
* Following Stuart's comments [3], I've added an overview [4] of what
the various ebuild.sh QA notices mean and how to fix them. I'll be
adding in other similar material such as how to fix sandbox violations
-- requests welcomed.
* Following Tom's comments, I've started a section on arch things [5].
This isn't intended to be comprehensive; it's just a simple overview for
non arch people so that they can have some vague clue about what the
heck the mips guys mean when they say "this doesn't work on n32". Thanks
to the sparc and mips teams for their help and contributions. Currently
sparc and mips are the only archs covered in depth, because they're all
I know -- it would be much appreciated if other arch teams would like to
lend a hand.
* Following all kinds of people's comments, I've started a section
[6] which is known as the 'tasks reference' until I come up with a less
sucky name. Thanks to Aaron for the Bash Completion [7] things and Diego
for his commentary on PAM [8].
* More autotools [9] updates. It's getting there... I added some more
lines to the picture too.
Suggestions, contributions [10], requests, clarifications, hints about
the many many typos, complaints etc to me via email.
Again, if anyone wants me to shut up about this thing or take it down,
just let me know.
1: http://www.firedrop.org.uk/devmanual/
2: http://dev.gentoo.org/~ciaranm/
3: http://tinyurl.com/bfntq
4: http://www.firedrop.org.uk/devmanual//appendices/common-problems/#
5: http://www.firedrop.org.uk/devmanual//archs/#
6: http://www.firedrop.org.uk/devmanual//tasks-reference/#
7: http://www.firedrop.org.uk/devmanual//tasks-reference/completion/
8: http://www.firedrop.org.uk/devmanual//tasks-reference/pam/
9: http://www.firedrop.org.uk/devmanual//general-concepts/autotools/#
10: http://www.firedrop.org.uk/devmanual/appendices/contributing/
--
Ciaran McCreesh : #2 Gentoo Whipping Monkey
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-05-22 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-22 8:35 Ciaran McCreesh [this message]
2005-05-22 8:59 ` [gentoo-dev] RFC: slight deunofficialisation of Unofficial Gentoo Development Guide Mike Frysinger
2005-05-22 9:08 ` Ciaran McCreesh
2005-05-22 15:35 ` Lance Albertson
2005-05-25 7:47 ` Ciaran McCreesh
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=20050522093542.2f5dfda2@snowdrop \
--to=ciaranm@gentoo.org \
--cc=gentoo-dev@lists.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