Re: cvs commit: ports/sysutils/xfce4-utils Makefile

2011-12-20 Thread Chris Rees
On 20 Dec 2011 06:53, "Chris Rees" wrote: > > On 20 Dec 2011 00:11, "Doug Barton" wrote: > > > > On 12/19/2011 02:03, Chris Rees wrote: > > > > > > On 19 Dec 2011 09:59, "Doug Barton" > > > wrote: > > >> > > >> Thanks, that's 1/3 of the job done. :) The problem is that

Re: cvs commit: ports/sysutils/xfce4-utils Makefile

2011-12-19 Thread Chris Rees
On 20 Dec 2011 00:11, "Doug Barton" wrote: > > On 12/19/2011 02:03, Chris Rees wrote: > > > > On 19 Dec 2011 09:59, "Doug Barton" > > wrote: > >> > >> Thanks, that's 1/3 of the job done. :)  The problem is that the current > >> OPTION creates the false idea that the only

Re: cvs commit: ports/sysutils/xfce4-utils Makefile

2011-12-19 Thread Doug Barton
On 12/19/2011 02:03, Chris Rees wrote: > > On 19 Dec 2011 09:59, "Doug Barton" > wrote: >> >> Thanks, that's 1/3 of the job done. :) The problem is that the current >> OPTION creates the false idea that the only way you can lock your screen >> is to use xlockmore. >> >>

Re: cvs commit: ports/sysutils/xfce4-utils Makefile

2011-12-19 Thread Chris Rees
On 19 December 2011 10:03, Chris Rees wrote: > > On 19 Dec 2011 09:59, "Doug Barton" wrote: >> >> Thanks, that's 1/3 of the job done. :)  The problem is that the current >> OPTION creates the false idea that the only way you can lock your screen >> is to use xlockmore. >> >> Perhaps you missed my

Re: cvs commit: ports/sysutils/xfce4-utils Makefile

2011-12-19 Thread Mark Linimon
On Mon, Dec 19, 2011 at 01:59:13AM -0800, Doug Barton wrote: > Thanks, that's 1/3 of the job done. :) I agree that the ideal situation is that committers complete whatever followup work is/are common-sense consequences of their commits. mcl ___ freebsd-

Re: cvs commit: ports/sysutils/xfce4-utils Makefile

2011-12-19 Thread Chris Rees
On 19 Dec 2011 09:59, "Doug Barton" wrote: > > Thanks, that's 1/3 of the job done. :) The problem is that the current > OPTION creates the false idea that the only way you can lock your screen > is to use xlockmore. > > Perhaps you missed my followup where I mentioned that the next step > would b

Re: cvs commit: ports/sysutils/xfce4-utils Makefile

2011-12-19 Thread Doug Barton
Thanks, that's 1/3 of the job done. :) The problem is that the current OPTION creates the false idea that the only way you can lock your screen is to use xlockmore. Perhaps you missed my followup where I mentioned that the next step would be to add an OPTION for xscreensaver as well, and the logi

Re: cvs commit: ports/sysutils/xfce4-utils Makefile

2011-12-12 Thread Olivier Duchateau
2011/12/12 Doug Barton : > On 12/12/2011 13:38, Rene Ladan wrote: >> On 12-12-2011 22:23, Doug Barton wrote: >>> Not only is this not necessary if you run xscreensaver already, it's >>> probably a bad idea. At minimum, can you make this optional? >>> >> [cvs-lists omitted] >> >> I could make it opt

Re: cvs commit: ports/sysutils/xfce4-utils Makefile

2011-12-12 Thread Doug Barton
On 12/12/2011 13:38, Rene Ladan wrote: > On 12-12-2011 22:23, Doug Barton wrote: >> Not only is this not necessary if you run xscreensaver already, it's >> probably a bad idea. At minimum, can you make this optional? >> > [cvs-lists omitted] > > I could make it optional if you insist, but if you d

Re: cvs commit: ports/sysutils/xfce4-utils Makefile

2011-12-12 Thread Rene Ladan
On 12-12-2011 22:23, Doug Barton wrote: > Not only is this not necessary if you run xscreensaver already, it's > probably a bad idea. At minimum, can you make this optional? > [cvs-lists omitted] I could make it optional if you insist, but if you do a fresh install with xfce4-utils but without xl

Re: cvs commit: ports/sysutils/xfce4-utils Makefile

2011-12-12 Thread Doug Barton
Not only is this not necessary if you run xscreensaver already, it's probably a bad idea. At minimum, can you make this optional? Doug On 12/11/2011 04:56, Rene Ladan wrote: > rene2011-12-11 12:56:18 UTC > > FreeBSD ports repository > > Modified files: > sysutils/xfce4-utils M