On Wed, Feb 15, 2006 at 08:25:07PM +0300, =?UTF-8?Q?
=D0=9F=D0=BE=D1=80=D1=82=D0=BE=D0=BD_?=
=?UTF-8?Q?=D0=9B=D1=8C=D0=B2=D0=BE=D0=B2=D0=B8=D1=87 ?= wrote:
> First, I suggested .zip just for an example. There are other similar
> archivers with bigger compression ratio.
>
>
> One
Портон Виктор Львович <[EMAIL PROTECTED]> writes:
> Not always. For example, apache2 package is split into two packages:
> apache2 and apache2-doc (and also apache2-dev and several others). To
> Build apache2 binary package most of documentation files are not
> needed. In the case of apache2 downl
First, I suggested .zip just for an example. There are other similar archivers
with bigger compression ratio.
>> 3. Users could be then able to mount a .zip file from the Debian FTP
server
>> and compile a package directly from the server. This would reduce
download
>> I deem some about 50% compa
ke, 2006-02-15 kello 04:00 +0500, Victor Porton kirjoitti:
> Here is my plan how to reduce Debian servers load and users Debian packages
> download bandwidth:
>
> 1. Package in .zip (or a similar format) instead of .tar.{gz,bz2}
Picking a random package:
-rw-rw-r-- 1 liw liw 18113820 Mar 18 2
Package: general
Severity: wishlist
Here is my plan how to reduce Debian servers load and users Debian packages
download bandwidth:
1. Package in .zip (or a similar format) instead of .tar.{gz,bz2}
2. Implement ZIP filesystem as Linux kernel module.
3. Users could be then able to mount a .zip f
5 matches
Mail list logo
