From: Erik Mouw <erik@harddisk-recovery.com>
To: Karel Kulhav? <clock@twibright.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: make htmldocs
Date: Tue, 14 Oct 2003 13:04:13 +0200 [thread overview]
Message-ID: <20031014110413.GC15075@bitwizard.nl> (raw)
In-Reply-To: <20031014120946.A4969@beton.cybernet.src>
On Tue, Oct 14, 2003 at 12:09:46PM +0200, Karel Kulhav? wrote:
> > > 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.
Not the problem of the kernel. If you can build your whole system
manually, you also know how to use Google.
> Asking again: how do I install "DocBook stylesheets"?
Replying again: Depends on distribution. (On Debian: apt-get install
docbook docbook-dsssl).
> 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.
Distributions tend to package these kind of projects. DocBook is one of
the projects that has been packaged by the distributions. GCC is
another project.
> 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.
DocBook is not necessary to *build* the kernel. It's only used to make
nicely formatted documents from the comments already in the kernel
source or to make nicely formatted documents from the source of the
books in Documentation/DocBook/. If you don't have DocBook available,
that doesn't make the kernel less portable, all documentation is
available in a human readable format.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
| Data lost? Stay calm and contact Harddisk-recovery.com
next prev parent reply other threads:[~2003-10-14 11:04 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ý
2003-10-14 10:48 ` Clemens Schwaighofer
2003-10-14 11:04 ` Erik Mouw [this message]
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=20031014110413.GC15075@bitwizard.nl \
--to=erik@harddisk-recovery.com \
--cc=clock@twibright.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