From: Leo Laursen <ll_news@stofanet.dk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Proposal for /usr/share/doc hierarchy
Date: Sat, 3 Apr 2004 08:10:42 +0200 [thread overview]
Message-ID: <20040403061042.GA11896@nagual.toltech.dk> (raw)
This was sent to gentoo-user, but I was informed that this list is more
apropriate
Hi. I am rather new to gentoo, so I don't know if this has been
discussed before.
On debian and now gentoo, one little irritating issue is the large
number of files in /usr/share/doc. On gentoo there is a very natural
solution by mirroring the portage tree in the doc directory.
Eg. /usr/share/doc/mutt-1.5.6 would be
/usr/share/doc/net-mail/mutt/mutt-1.5.6
It should be quite easy to implement (I think).
For those with USE=doc, packages could register html-documentation in
/usr/share/doc/html/<package> (perhaps symlink)
I would like very much to have a http://localhost/doc with persistant
filenames across package upgrade.
Leo
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2004-04-03 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-03 6:10 Leo Laursen [this message]
2004-04-03 7:34 ` [gentoo-dev] Proposal for /usr/share/doc hierarchy Matthew Kennedy
2004-04-03 22:32 ` Stuart Herbert
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=20040403061042.GA11896@nagual.toltech.dk \
--to=ll_news@stofanet.dk \
--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