view debian/postinst.templates @ 9177:01a713dcaf23

disable free() in string and string_list parsers. yes, it's a hack (and a little memleak), but i can explain :) [note it's just a few kB memleak, but it's the price of stability without full code review/audit - there are hunderds of possible double free()] the old config parser didn't free() strings/stringlists, but didn't even allocate them by default. the new one always free(), and it causes memcorruption/sig11 at cases like this: char* dvd_device="/dev/dvd"; {"dvd-device", &dvd_device, CONF_TYPE_STRING, 0, 0, 0, NULL}, since string constansts (allocated in .TEXT segment) cannot be free()'d

Template: mplayer/output
Type: select
Choices: ${vo}
Default: xv 
Description: Which Video Output driver would you like?
 Mplayer can use very wide range of video output drivers:
 ( order aproximately by speed: )
	 * mga, xmga - direct hardware access on MGA cards (G200/400/450), needs /dev/mga_vid
	   this driver can work without X and display video on secondary head of matrox cards
	 * xv - XVideo extensions of X 4.x ( hardware scaling, bilinear filtering )
	 * sdl - SDL library, it can also use hardware scaling, filtering etc 
	 * dga, fsdga - DGA extension.
	 * fsbdev - framebuffer device ( watching movies on text console )
	 * x11 - simple x11 output.
 Please choose carefully because it has tramendous effect on speed.

Template: mplayer/overwrite
Type: boolean
Default: false
Description: Overwrite /etc/mplayer/mplayer.conf ?
 Should I overwrite your current /etc/mplayer/mplayer.conf with the one created on the fly based on your answers?

Template: mplayer/cfgnote
Type: note
Description: Create your ~/.mplayer/conf file.
	Remember to read documentation and edit your ~/.mplayer/conf
	(or /etc/mplayer/mplayer.conf) file. This binary depends heavily on
	your hardware - which means that it needs tweaking for every single
	machine it's installed to. And it also it means that it will use
	your setup very effectively. Look at /usr/share/doc/mplayer
  end