Re: SOURCES: lighttpd-mod_staticfile.conf - revert, put this to new pa...

2008-04-27 Thread Pawel Golaszewski
On Sun, 27 Apr 2008, Elan Ruusamäe wrote: > > What is the rationale for putting it into new package? > to be same as lighttpd-php-external and lighttpd-php-spawned. > > what was reason there. i don't remember. there was something. a - graaat That explains everything... Maybe we'll s

Re: SOURCES: lighttpd-mod_staticfile.conf - revert, put this to new pa...

2008-04-27 Thread Elan Ruusamäe
On Sunday 27 April 2008 22:35, Pawel Golaszewski wrote: > What is the rationale for putting it into new package? to be same as lighttpd-php-external and lighttpd-php-spawned. what was reason there. i don't remember. there was something. if you really want to go your way, TEST the setup first (al

Re: SPECS (DEVEL): smplayer.spec - up to rc4

2008-04-27 Thread Piotr Budny
Dnia niedziela, 27 kwietnia 2008, Kamil Dziedzic napisał: > vip wrote: > > Author: vip Date: Sat Apr 19 22:30:13 2008 GMT > > Module: SPECS Tag: DEVEL > > Log message: > > - up to rc4 > > rc4 is marked as stable[1] by authors so I want to move i

Re: SOURCES: lighttpd-mod_staticfile.conf - revert, put this to new pa...

2008-04-27 Thread Pawel Golaszewski
On Sun, 27 Apr 2008, glen wrote: [...] > - revert, put this to new package if really needed [...] >lighttpd-mod_staticfile.conf (1.9 -> 1.10) [...] > -# .fcgi, .php, .pl are most often handled by mod_fastcgi or mod_cgi > -static-file.exclude-extensions = ( ".fcgi", ".php", ".pl" ) > +# .pl, .f

Re: SPECS (DEVEL): smplayer.spec - up to rc4

2008-04-27 Thread Kamil Dziedzic
vip wrote: > Author: vip Date: Sat Apr 19 22:30:13 2008 GMT > Module: SPECS Tag: DEVEL > Log message: > - up to rc4 > rc4 is marked as stable[1] by authors so I want to move it to HEAD. Any objections? [1] http://smplayer.sourceforge.net/downl

Re: dir for initrd progs

2008-04-27 Thread Elan Ruusamäe
On Sunday 27 April 2008 16:25, Tomasz Pala wrote: > As above - are these some alternate versions useless during normal > system work? they are not useless (well i know only busybox-initrd is useless), but you just do not use them. and > It would be easier if you give some examples. hard to giv

Re: dir for initrd progs

2008-04-27 Thread Tomasz Pala
On Sun, Apr 27, 2008 at 13:22:04 +0300, Elan Ruusamäe wrote: > these programs are not to be used from regular system, State them, let's talk about the ones, not some ones. > there are shared > versions of same (and usually more featured) programs. [1] In that case it's ok for me. > > > %{_lib

Re: SPECS: lm_sensors.spec - up to 3.0.1, kernel >= 2.6.5

2008-04-27 Thread Elan Ruusamäe
On Sunday 27 April 2008 15:32, wolvverine wrote: > +Requires:  kernel >= 2.6.5 no userspace -> kernel deps allowed. think of custom built kernel. however you may use: Requires:uname(release) >= 2.6.5 -- glen ___ pld-devel-en mailing list pld-d

Re: dir for initrd progs

2008-04-27 Thread Elan Ruusamäe
On Sunday 27 April 2008 12:45:48 Tomasz Pala wrote: > On Sun, Apr 27, 2008 at 12:15:29 +0300, Elan Ruusamäe wrote: > > how about putting programs that were compiled to be put to initrd into > > own dir instead of filling up /sbin with them? > > And how about putting libraries in /home and temporary

Re: dir for initrd progs

2008-04-27 Thread Tomasz Pala
On Sun, Apr 27, 2008 at 12:15:29 +0300, Elan Ruusamäe wrote: > how about putting programs that were compiled to be put to initrd into own > dir > instead of filling up /sbin with them? And how about putting libraries in /home and temporary files in /usr/share? > or maybe organize them already

dir for initrd progs

2008-04-27 Thread Elan Ruusamäe
hi how about putting programs that were compiled to be put to initrd into own dir instead of filling up /sbin with them? %{_libdir}/initrd or maybe organize them already in hierarchy that initrd would have? %{_libbdir}/sbin %{_libbdir}/bin %{_libbdir}/lib %{_libbdir}/etc -- glen