From: "Igor Gueths" <igueths@yahoo.com>
To: <speakup@braille.uwo.ca>
Subject: Re: trplayer and realplayer
Date: Fri, 8 Mar 2002 17:08:16 -0500 [thread overview]
Message-ID: <008101c1c6ed$c015fda0$01213e18@OEMCOMPUTER> (raw)
In-Reply-To: <Pine.LNX.4.44.0203082345250.387-100000@borg.goanna.net.au>
Hi Shaun. I will be doing this thing with trplayer sometime in the future, so I figured I would try to clarify one point here. When you copy the libs to /usr/lib and the untar the trplayer archive, doesn't it create its own directory? Or does trplayer come in source? Because then your point about installing the binary makes sense, because you have to compile the source. But if it is just a binary, you should just be able to extract it from the archive and you can just run it from there? Just wanted to know whether or not the trplayer package was archived as source or as a binary.
----- Original Message -----
From: Shaun Oliver <shauno@goanna.net.au>
To: <speakup@braille.uwo.ca>
Sent: Friday, March 08, 2002 7:48 AM
Subject: Re: trplayer and realplayer
> On Thu, 7 Mar 2002, Deedra Waters wrote:
>
> > hmm, ok, I must be doing something wrong. I got the realplayer thing off
> > of the ftp websight like shawn said. the readme file has no instructions
> > on how to install it at all. only thing I can really guess at, is that I
> > don't need to install anything then for it?
> no. all you need to do is copy the libs to /usr/lib and then tar zxvf the
> archive and you're set.
> then install the trplayer binary and it's all done.
> hth
> > > >
> > >
> > > --
> > > qShaun Oliver
> > >
> > > Marriage is a three ring circus:
> > > engagement ring, wedding ring, and suffering.
> > > -- Roger Price
> > >
> > > Email: shauno@goanna.net.au
> > > Icq: 76958435
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
> --
> qShaun Oliver
>
> Marriage is a three ring circus:
> engagement ring, wedding ring, and suffering.
> -- Roger Price
>
> Email: shauno@goanna.net.au
> Icq: 76958435
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
Deedra Waters
` Dave Hunt <
` Deedra Waters
` Dave Hunt <
` Deedra Waters
` Igor Gueths
` Shaun Oliver
` Deedra Waters
` Shaun Oliver
` Igor Gueths [this message]
` Gregory Nowak
` Shaun Oliver
` Gregory Nowak
` Shaun Oliver
` Igor Gueths
` Charles Hallenbeck
` Igor Gueths
` Gregory Nowak
` Igor Gueths
` Charles Hallenbeck
` Gregory Nowak
` cp Pete
` cp Gregory Nowak
` cp Pete
` cp Thomas Ward
` cp Pete
` trplayer and realplayer Steve Holmes
` Pete
` Gregory Nowak
` Thomas Ward
` Dave Hunt <
` Thomas Ward
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='008101c1c6ed$c015fda0$01213e18@OEMCOMPUTER' \
--to=igueths@yahoo.com \
--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).