On Sat, 25 Feb 2012, Carlos R. Mafra escribió:

> On Sat, 25 Feb 2012 at 20:37:59 +0100, Kamil Rytarowski wrote:
> > On 25.02.2012 17:40, Rodolfo García Peñas wrote:
> > >This is an example to launch Window Maker using a script.
> > Please if possible send patches against debian subdirectory
> > separately. It's more readable.
> > 
> > I don't agree with /etc/GNUstep directory. I had a look into
> > packages, and everything (maybe except KDE) is using /etc/X11 as the
> > system configuration prefix.
> > 
> > I think we should even abandon this name and replace it with
> > "wmaker". It would be also nicer and safer to keep GNUstep hidden
> > from a common use and add a dot before its name; also renaming the
> > directory to ".wmaker".
> 
> I think by now it's tradition to use ~/GNUstep and I'm opposed to
> changing it.
 
I like the .wmaker idea (I prefer hiden configuration directories), and the 
~/GNUstep folder. IMO, we should think move to .wmaker and continue with 
GNUstep for backward compatibility. I think we only need include the .wmaker in 
the configuration path define. Then, we can use .wmaker and GNUstep folders.

> And I'm not accepting this patch unless there's a way to avoid this
> script launch. I don't want to use a script to launch wmaker, but
> I do see that distros may want to do it.

I understand you, but I don't agree :-) If the distributions are using a 
script, probably is a good idea. IMO is better to be near of the distributions, 
because the users normally use them. The users (not developers) use 
debian/ubuntu/suse/fedora/... Even, I never run make install on my systems, 
sometimes I use a virtual machine. When the patches are finished, I build a 
debian package, then install it.

If we can include the same script for all distros, probably is better for all.

kix.

> So please make this depend on a --launch-script option to configure.
> 
> 
> -- 
> To unsubscribe, send mail to [email protected].

-- 
||// //\\// Rodolfo "kix" Garcia
||\\// //\\ http://www.kix.es/


--
To unsubscribe, send mail to [email protected].

Reply via email to