Re: Static linked

Le Mardi 18 Février 2003 02:49, Mikael Hallendal a écrit :
> tis 2003-02-18 klockan 01.43 skrev Xtian Xultz:
> > Hi MrProject gurus!
> >
> > Im trying to compile MrProject 0,9 on a Mandrake 9.0 but it needs some
> > dependencies, and the dependencies more dependencies, and it goes "ad
> > eternum"...
> >
> > So, what about a static binary package? Even having a not so old distro,
> > it becomes hard to install, and I think it would help a lot of people...
>
> I'm pretty sure that MrProject 0.9 will end up in cooker pretty soon.
> Not even sure it's possible to make a statically linked binary of
> MrProject, and if it where it would probably be huge.
>
> Frederic has been very quick to add MrProject releases in the past so
> just wait a week or so and you'll get it in.
>
> Regards,
>   Mikael Hallendal

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