[iPAQ] Getting Initimate and Famliar to play nice.

>snip<
>space. A *LOT* of libs are in multiple places. If they just have to be in
>each directory, linking would help. Also, a lot of stuff may not be wanted
>or needed. If you only use one browser, delete the others.
>snip<

Agreed. I think this should become clearer once everything is together
in packages.

>snip<
>Some form of compression for some types of files would help too.
>snip<

I think most of the executables are already gzexe'd. Is there such a thing
as bzexe? Is it possible to compress .glade files? xml tends to take up
a lot of space but compresses very well owing to all the duplicate tag
names. A lot of software reads plain text configuration files - could they
be persuaded to read bzipped files instead, and would doing so cause
other packages to break?

There is certainly a lot that *could* be done to save space, but it would
involve a *lot* of coordinated work. Is this the kind of thing that ought to
be in the distribution, or should it be left as 'Debianised' as possible?

Fully agree with you about the use of links, but again, this may be better
done by individuals as part of the 'tuning' process rather than in the
packages themselves (unless the packages are installing multiple
libraries in different places - which would be silly.) Even when it comes
to hard-linking files to the Familiar files in the flash could cause
complicated cross-distribution dependencies - upgrade to the latest
Familiar might cause Intimate to break. If the packages were intact, they
could just be re-installed to fix the problem, but if the packages contained
links, it would remain broken.

Perhaps more discussion needs to be done on the wiki...

Dave.
        
Received on Thu Mar 29 06:57:54 2001