From: Kenny Hitt <kenny@hittsjunk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: writing spk howto (?)
Date: Wed, 3 Nov 2004 07:00:35 -0600 [thread overview]
Message-ID: <20041103130035.GA29007@blackbox> (raw)
In-Reply-To: <20041103114035.GJ6259@rednote.net>
Hi. The ideal HOWTO in this case would hava a section for each distro.
I don't believe there is any easy way to just write instructions that
are independent of a specific distro.
For example, I only have to build speechd-up from CVS on my Debian box.
Unstable has a Debian package for speech-dispatcher 0.5. I believe the
version in testing is still at 0.4, but haven't checked.
I have to disagree with Chuck on this one. When I look for a HOWTO, I
try to find a Debian specific one first and only use a "general" HOWTO
as a last resort. I've found doing things my distro's way just makes my
life easier.
Kenny
On Wed, Nov 03, 2004 at 06:40:36AM -0500, Janina Sajka wrote:
> Well, I think it would not be hard to point at all kinds of
> documentation that misses one major point or another.
>
> Fact is, dependencies are important and a system's functionality can
> easily become impaired by failing to manage dependencies appropriately.
> It seems to me the fact that so few of us build our Linux installations
> from scratch is ample testimony to this fact.
>
> As far as I now, there are not any package files for speechd-up as of
> yet. If memroy serves, there is a .deb for speech-dispatcher. Do you
> really think it doesn't matter whether a someone uses the package or
> attempts to build from scratch? Isn't it even more important for a
> newbie to understand this?
>
> Chuck Hallenbeck writes:
> > Sure. That would be great. But I have often read a howto that addresses
> > only a single distro, relying on distro specific stuff, with no notion
> > that people using other distros might be out there as well. We get
> > enough of that from Redmond.
> >
> >
> > On Tue, 2 Nov 2004, Janina Sajka wrote:
> >
> > >I aggree with you in a general way, but wonder whether you'd also agree
> > >that one should, when possible, stick to standard procedures on one's
> > >distro. In other words, when on Debian, install a .deb if you can, and
> > >when on Fedora, use an rpm if you can, etc., etc.
> > >
> > >Chuck Hallenbeck writes:
> > >>David,
> > >>
> > >>I presently have software speech running on my Slackware 10.0 distro,
> > >>using version 0.5rc3 of speech-dispatcher, and would be happy to share
> > >>my setup with you or help in any other way with the howto. It would be a
> > >>valuable contribution to make such a document available, particularly if
> > >>it were not specific to any one distro.
> > >>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
David Bruzos
` Thomas Stivers
` Janina Sajka
` Willem van der Walt<willem@top.health.gov.za>
` hank
` Chuck Hallenbeck
` Janina Sajka
` Chuck Hallenbeck
` Willem van der Walt<willem@top.health.gov.za>
` Janina Sajka
` Kenny Hitt [this message]
` Chuck Hallenbeck
` Janina Sajka
` Sean McMahon
` Janina Sajka
` Sean McMahon
` Janina Sajka
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=20041103130035.GA29007@blackbox \
--to=kenny@hittsjunk.net \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).