[gentoo-dev] Issues with mplayer-0.18pre ebuild

[gentoo-dev] Issues with mplayer-0.18pre ebuild

[Karl Trygve Kalleberg]

This ebuild does not install /etc/mplayer.conf.

Is there any particular reason for this ?

To get it to run, the codecs.conf.gz must be manually installed in
.mplayer/codecs.conf by each user, which is unneccessarily cumbersome.

Does anybody (Bruce ?) have more detailed knowledge about this ?


Regards,

Karl T

Re: [gentoo-dev] Issues with mplayer-0.18pre ebuild

[Martin Schlemmer]

On Thu, 2001-09-20 at 23:27, Karl Trygve Kalleberg wrote:
> This ebuild does not install /etc/mplayer.conf.
> 
> Is there any particular reason for this ?
> 
> To get it to run, the codecs.conf.gz must be manually installed in
> .mplayer/codecs.conf by each user, which is unneccessarily cumbersome.
> 
> Does anybody (Bruce ?) have more detailed knowledge about this ?
> 

Problem with having a devault /etc/mplayer.conf, is that mplayer can 
have so many different setup's.  Should it use SDL, OpenGL, X11, XV,
framebuffer dev,etc for video?  And what about sound ?

I am no .ebuild expert, nor mplayer, although it is the video player
I use by default, but am prepared to hack the mplayer .ebuild a bit.
All I need is some suggestions as how to handle the .conf file?

Do we:
1) look for X in USE, if so make libSDL a required depend and install
   a .conf that use SDL for sound and video (since SDL can make use of
   accel and also autodetect the sound ...)?
2) if ! X in USE, assume that the framebuffer dev will be used and
   install a .conf accordingly ?

This is the easiest way of doing it as far as I can see.  X11 do not 
give decent output, and determining if OpenGL sould be used, or XV, or
DGE, etc can be difficult, and since SDL can autodetect this, it should
make things easier ... same with audio ....


Some suggestions will be appreciated.

Greetings
MS

Re: [gentoo-dev] Issues with mplayer-0.18pre ebuild

[Mikael Hallendal]

fre 2001-09-21 klockan 00.35 skrev Martin Schlemmer:

> I am no .ebuild expert, nor mplayer, although it is the video player
> I use by default, but am prepared to hack the mplayer .ebuild a bit.
> All I need is some suggestions as how to handle the .conf file?
> 
> Do we:
> 1) look for X in USE, if so make libSDL a required depend and install
>    a .conf that use SDL for sound and video (since SDL can make use of
>    accel and also autodetect the sound ...)?
> 2) if ! X in USE, assume that the framebuffer dev will be used and
>    install a .conf accordingly ?

This might be one way of doing it. We can also install a default .conf
with all options outcommented in them and then the user uncomment the
stuff he wants.

Both these ways can be combined of course. To uncomment FB-stuff if X is
not in USE ...

Regards,
  Mikael Hallendal

-- 

Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden

Re: [gentoo-dev] Issues with mplayer-0.18pre ebuild

[Karl Trygve Kalleberg]

On Fri, Sep 21, 2001 at 12:35:49AM +0200, Martin Schlemmer wrote:
> Do we:
> 1) look for X in USE, if so make libSDL a required depend and install
>    a .conf that use SDL for sound and video (since SDL can make use of
>    accel and also autodetect the sound ...)?
> 2) if ! X in USE, assume that the framebuffer dev will be used and
>    install a .conf accordingly ?
> 
> This is the easiest way of doing it as far as I can see.  X11 do not 
> give decent output, and determining if OpenGL sould be used, or XV, or
> DGE, etc can be difficult, and since SDL can autodetect this, it should
> make things easier ... same with audio ....

It would seem that you have a prioritized list of options on which graphics
library we should use.

I would suggest that the ebuild goes through that list in prioritized order,
checks which are installed, and if none, have a fallback in place.

SDL as a fallback on X is okay.

Same thing with sound.

If, for some reason, this turnes out to be impossible, you must at least
make a note in post_install() about the fact that the user himself needs to
customize the /etc/mplayer.conf file.

Karl T

Re: [gentoo-dev] Issues with mplayer-0.18pre ebuild

[Mikael Hallendal]

lör 2001-09-22 klockan 12.17 skrev Karl Trygve Kalleberg:
> On Fri, Sep 21, 2001 at 12:35:49AM +0200, Martin Schlemmer wrote:
>
> It would seem that you have a prioritized list of options on which graphics
> library we should use.

I'm not familiar with mplayer or libSDL for that matter. Just giving an
example.
 
> If, for some reason, this turnes out to be impossible, you must at least
> make a note in post_install() about the fact that the user himself needs to
> customize the /etc/mplayer.conf file.

This depends on what userbase we have/want to have. Most packages you
install you want to check the config before you are using them. So I
don't think we have to mention everytime there are a configure-file
available in a package.

Most of our current users are advanced Linux users and doesn't need to
be told about the possibility to configure packages.

Regards,
  Mikael Hallendal

-- 
Mikael Hallendal                micke@codefactory.se
CodeFactory AB                  http://www.codefactory.se/
Office: +46 (0)8 587 583 05     Cell: +46 (0)709 718 918

Re: [gentoo-dev] Issues with mplayer-0.18pre ebuild

[Karl Trygve Kalleberg]

On Sat, Sep 22, 2001 at 12:31:08PM +0200, Mikael Hallendal wrote:

> This depends on what userbase we have/want to have. Most packages you
> install you want to check the config before you are using them. So I
> don't think we have to mention everytime there are a configure-file
> available in a package.
> 
> Most of our current users are advanced Linux users and doesn't need to
> be told about the possibility to configure packages.

I'm not advocating "dumbing down" our users; but I do think it only fair
to make a notice to the user that "this package does, contrary to what one
would expect, does not work without manual configuration".

I find it repulsive that I have to manually configure my video player to
get it to run at all. I have not problems accepting that I will have to
manually tweak it to obtain optimal performance. But the point of using a
distro (any kind of distro) in the first place was to avoid doing all the
strictly unnecessary details. I would expect the packagers to set up
reasonable defaults in the configuration files, whenever that is possible.

In this specific case, it seems to be very possible, since what I did to
get mplayer to run was simply unpack the codecs.conf.gz file into
.mplayer/codecs.conf of the user that should run mplayer, and it all
worked okay.


Kind regards,

Karl T

Re: [gentoo-dev] Issues with mplayer-0.18pre ebuild

[Collins Richey]

On Sat, 22 Sep 2001 16:46:32 +0200 Karl Trygve Kalleberg
<karltk@prosalg.no> wrote:

> On Sat, Sep 22, 2001 at 12:31:08PM +0200, Mikael Hallendal wrote:
> 
> > This depends on what userbase we have/want to have. Most packages
> you
> > install you want to check the config before you are using them. So
> I
> > don't think we have to mention everytime there are a
> configure-file
> > available in a package.
> > 
> > Most of our current users are advanced Linux users and doesn't
> need to
> > be told about the possibility to configure packages.
> 
> I'm not advocating "dumbing down" our users; but I do think it only
> fair
> to make a notice to the user that "this package does, contrary to
> what one
> would expect, does not work without manual configuration".
> 
> I find it repulsive that I have to manually configure my video
> player to
> get it to run at all. I have not problems accepting that I will have
> to
> manually tweak it to obtain optimal performance. But the point of
> using a
> distro (any kind of distro) in the first place was to avoid doing
> all the
> strictly unnecessary details. I would expect the packagers to set up
> reasonable defaults in the configuration files, whenever that is
> possible.
> 
> In this specific case, it seems to be very possible, since what I
> did to
> get mplayer to run was simply unpack the codecs.conf.gz file into
> .mplayer/codecs.conf of the user that should run mplayer, and it all
> worked okay.
> 

I would have to agree whole-heartedly.  I do not believe that gentoo
have undertaken all the effort required to setup this wonderful distro
with the intent of having it remain a distro that can only be
installed by senior linux administrators and gurus.  It would require
relatively little effort to to add a post-install configuration
document to any package under the emerge/ebuild system that requires
manual configuration.  Initially this could be just a link to the
appropriate authoritative documentation for the package, but
eventually the documentation should include instructions that can be
easily understood by most users.


-- 
Collins Richey
Denver Area
gentoo_rc6 xfce+sylpheed

Re: [gentoo-dev] Issues with mplayer-0.18pre ebuild (mplayer-0.18pre-r1.ebuild)

[Martin Schlemmer]

[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]

On Sat, 2001-09-22 at 16:46, Karl Trygve Kalleberg wrote:

> I'm not advocating "dumbing down" our users; but I do think it only fair
> to make a notice to the user that "this package does, contrary to what one
> would expect, does not work without manual configuration".
> 
> I find it repulsive that I have to manually configure my video player to
> get it to run at all. I have not problems accepting that I will have to
> manually tweak it to obtain optimal performance. But the point of using a
> distro (any kind of distro) in the first place was to avoid doing all the
> strictly unnecessary details. I would expect the packagers to set up
> reasonable defaults in the configuration files, whenever that is possible.
> 
> In this specific case, it seems to be very possible, since what I did to
> get mplayer to run was simply unpack the codecs.conf.gz file into
> .mplayer/codecs.conf of the user that should run mplayer, and it all
> worked okay.
> 

hehe

ok, here is updated mplayer .ebuild.  It tries to use the USE variable
to construct a /etc/mplayer.conf.

also added is w32codecs-0.18.ebuild, which should go to media-libs, and
is a depend of mplayer-0.18_pre-r1

in detecting what config should be used, worked as follow:
 
Video: if use X: sdl -> ggi -> gl -> x11
       if ! use X: fbdev -> svga

Audio sdl -> alsa -> oss -> esd

I think we need another USE variable XV for XVideo extension, since it
is more usable than gl, and a few apps use it, will use in future.


greetings
MS

[-- Attachment #2: mplayer.tar.bz2 --]
[-- Type: application/x-bzip, Size: 5536 bytes --]

[-- Attachment #3: w32codecs-0.18.ebuild --]
[-- Type: text/plain, Size: 455 bytes --]

# Copyright 1999-2000 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License, v2 or later
# Author Martin Schlemmer <azarah@saintmail.net>

S=${WORKDIR}
DESCRIPTION="Win32 binary codecs for MPlayer and maybe avifile as well."
SRC_URI="ftp://ftp.mplayerhq.hu/MPlayer/releases/w32codec.zip"
HOMEPAGE="http://www.mplayerhq.hu/"

DEPEND=""

src_install () {
	cd ${S}
	
	dodir /usr/lib/win32
	cp ${S}/* ${D}/usr/lib/win32
}