Re: Static linked

Here in Brazil we have a expression that says: you taked the words from
my mounth. 

My Linux box serves to 9 terminals running LTSP, and all my work stops
if my application server stops. 

Update all the dependencies from Cooker is a big risk to me (and a lot
of people too).


> I'm agree, static linked binary could be huge
> but you discard a big part of users
> (and in the same time some testers)
> from using MrProject.
> I think it would not be good
> for the quality of MrProject software.
> Moreover, user can't give effective feedback
> since they don't benefit from updates.
> 
> I think that distros have to use
> dynamically linked binaries
> because it keep from being huge
> in disk space and memory usage.
> But think at users who are frustrated
> because they have not the last fashion of distro.
> 
> I use the latest version of a distro (Mandrake 9.0, 6 months old)
> but the version of MrP I use still be 0.6.
> I tried to update to MrP 0.8 using Mandrake Cooker
> but there are 2 reason which bring me to give up :
> - Mandrake Cooker is 'experimental' (see Mandrake Cooker home page)
>   and I can't use experimental features on a production environnement,
> - trying to update MrP 0.8 causes
>   more than 100 package updates
>   which could break my system
>   (that I use for my work).
> 
> The makefile could be used
> to generate a bzip2ed static linked binary
> for each new release (~ each 3 months).
> 
> 
> Jérôme
> 
> _______________________________________________
> MrProject mailing list
> [email protected]
> http://lists.codefactory.se/mailman/listinfo/mrproject