Re: ideas for returning memory to the OS

* Brian Crowder <[email protected]> wrote:
> 
> > At some point you have to *expect* an working base system.
> > And if, for example, M$'s libc is too broken, why not choose
> > another (free) one ?
> >
> 
> How should we maintain and deploy it?  

Same as with any other 3rd party package: not your job
("you" = the mozilla project) ;-P

> Are we allowed to keep a "frozen", locally maintained version 
> of it in our own source repositories?  Are we allowed to include 
> it in our build ? 

No. You should just clean *import* these packages and expect them 
to be existing on the target system. With this simple constraint, 
development and maintenance complexity breaks down dramatically.

> Or should we be tasked with educating over a hundred million 
> users in installing their own?

Please leave this to the distros. 

If you want some self-contained package for certain targets, 
feel free to build specific distros for them. As soon as mozilla 
(and imported packages) are cleanly crosscompile'able and use 
an easy-interceptible tool like pkg-config, this is almost trivial
without any additional support of the built packages (I've got my
own distro builder which does those jobs almost 100% automatically)


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------