discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSCharacterSet bloat?


From: Derek Zhou
Subject: Re: NSCharacterSet bloat?
Date: 25 Jan 2006 11:11:59 -0800
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3

Richard Frith-Macdonald <richard@brainstorm.co.uk> writes:

> On 24 Jan 2006, at 18:53, Derek Zhou wrote:
> 
> > gcc (or any lib that gnustep depends on) is public known free
> > software, while the utility to produce the characterset is not even
> > mentioned on gnustep.org
> 
> Not sure what you are trying to say.
> True, all the software (gcc, charset utilities, libraries etc) is
> 'public known free software', but that has nothing to do with being
> mentioned on gnustep.org and has nothing to do with whether it gets
> included in the base library (other than the fact that we would not
> include anything that isn't free software of course).  Also not sure
> why you talk about libs that gnustep depends upon.  Perhaps you think
> that we are using private, non-free software here ... if so that's is
> an incorrect and rather strange assumption which ought to have been
> dispelled by looking at the readme file and/or the source code.
> 
If I gave you the impression that I am accusing you of using non-free
software and hiding it, then I am sorry for not making myself
clear. What I was puzzled about is why a smallish utility (handful of
files), which propabably have little pratical usage other than in
base, lives outside the base. 
Anyway, I can put all the relevent files into the NSCharacterSet dir
under base and give you a tar ball and a patch to plug it in the
overall makefile.  
> 
> I think it's better to stick to saying that you have a personal
> aesthetic issue here ...
Another benefit of seperation is to give users the option of updating
charset data without recompiling base themselves. If gunstep goes
mainstream, most likely people will get gnustep from distributions and
refrain from manual installation (could mess up dependency).       

Derek




reply via email to

[Prev in Thread] Current Thread [Next in Thread]