From: "Karel Kulhavý" <clock@twibright.com>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: make htmldocs
Date: Tue, 14 Oct 2003 12:09:46 +0200 [thread overview]
Message-ID: <20031014120946.A4969@beton.cybernet.src> (raw)
In-Reply-To: <20031014094601.GB15075@bitwizard.nl>; from erik@harddisk-recovery.com on Tue, Oct 14, 2003 at 11:46:02AM +0200
On Tue, Oct 14, 2003 at 11:46:02AM +0200, Erik Mouw wrote:
> On Mon, Oct 13, 2003 at 06:55:39PM +0200, Karel Kulhav? wrote:
> > *** You need to install DocBook stylesheets ***
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > 1) What is DocBook stylesheets?
>
> Standard SGML representation system for technical documents.
Is it a program, set of documents or what? Is it self-contained
anywhere so I can download that at once?
Coul you please point me to a specification of an object called
"DocBook stylesheets"?
>
> > 2) How do I install DocBook stylesheets?
>
> Depends on distribution.
How do I determine what distribution I have? I have compiled my whole system
manually.
Asking again: how do I install "DocBook stylesheets"?
>
> > 3) Bugreport: there should be written
> > "Linux kernel depends on DocBook stylesheets. You may download DocBook
> > stylesheets here-and-there." in README
>
> Depends on distribution. We also don't tell for every distribution
> where to get gcc and how to install it.
Do you say that the place where DocBook stylesheet sources can be downloaded
depends on distribution I have? I have been looking at their sourceforge
project page but there is nothing like "download DocBook stylesheets".
There are DocBook-dsssl and a ton of other cryptic packages but none of them
is stylesheets.
If there doesn't exist any distribution-idependent installation process
for "DocBook stylesheets", then "DocBook stylesheets" is not portable,
and transitively, "Linux Kernel" is not portable. Could you please
recommend me some other open-source free operating system where I don't
need to have a "distribution" to be even able to read it's enclosed
documentation? I have been using Linux Kernel for 7 years but can't anymore
because I am unable to read it's manual.
Cl<
next prev parent reply other threads:[~2003-10-14 10:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 16:55 make htmldocs Karel Kulhavý
2003-10-14 9:46 ` Erik Mouw
2003-10-14 10:09 ` Karel Kulhavý [this message]
2003-10-14 10:48 ` Clemens Schwaighofer
2003-10-14 11:04 ` Erik Mouw
2003-10-14 12:57 ` Karel Kulhavý
2003-10-14 11:16 ` Michael Still
2003-10-14 13:44 ` Karel Kulhavý
[not found] ` <200310140842.57178.shawnfu@willden.org>
2003-10-14 15:06 ` make htmldocs -- docbook-utils Karel Kulhavý
2003-10-14 19:50 ` make htmldocs Michael Still
2003-10-14 14:09 ` Karel Kulhavý
2003-10-15 19:37 ` Thomas Horsten
2003-10-16 19:26 ` Pavel Machek
2003-10-14 14:41 ` Karel Kulhavý
2003-10-14 19:55 ` Michael Still
2003-10-14 21:53 ` Michael Still
2003-10-14 12:51 ` Pavel Machek
2003-10-14 17:29 ` Guy
2003-10-14 17:52 ` Sam Ravnborg
2003-10-15 19:30 ` Thomas Horsten
2003-10-15 11:01 ` Jean Charles Delepine
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=20031014120946.A4969@beton.cybernet.src \
--to=clock@twibright.com \
--cc=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.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