Re: Sizes and Packages in dselect

1995-10-04 Thread Ian Jackson
Raul Miller writes ("Re: Sizes and Packages in dselect"): > Ian Jackson: >This is where the problem starts :-). Obviously this can be done >fairly easily if you're willing to have the user download a list of >all the files included in every package,

Re: Sizes and Packages in dselect

1995-10-04 Thread stick
m (Smail3.1.28.1 #15) > id m0t0IiA-000D7iC; Tue, 3 Oct 95 18:33 PDT > Old-Return-Path: <[EMAIL PROTECTED]> > Message-Id: <[EMAIL PROTECTED]> > Date: Wed, 4 Oct 95 02:31 BST > From: Ian Jackson <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re:

Re: Sizes and Packages in dselect

1995-10-04 Thread Bill Mitchell
On Wed, 4 Oct 1995, Ian Jackson wrote: [...] > > For each file in the files list, find the deepest existing directory > ^^^ > > This is where the problem starts :-). Obviously this can be done > fairly easily if you're willing to have the user download a list of >

Re: Sizes and Packages in dselect

1995-10-03 Thread Raul Miller
Ian Jackson: This is where the problem starts :-). Obviously this can be done fairly easily if you're willing to have the user download a list of all the files included in every package, plus their sizes. I don't think that's reasonable, though; even compressed, the Contents file f

Re: Sizes and Packages in dselect

1995-10-03 Thread Ian Jackson
Bruce Perens writes ("Re: Sizes and Packages in dselect "): > I think I have the algorithm to do this. Please see if the following makes > sense. I can give you pseudocode (or real code) if necessary. > > For each file in the files list, find the deep

Re: Sizes and Packages in dselect

1995-10-03 Thread Bill Mitchell
On Tue, 3 Oct 1995, Bruce Perens wrote: > [... good thinking snipped ...] > Does this make sense? I can elaborate if you like. One additional point occurs to me. Some packages (perl? others?) consume significant space in postint processing. Size info for this could be ballparked by the maintai

Re: Sizes and Packages in dselect

1995-10-03 Thread Bruce Perens
[EMAIL PROTECTED] said: > I can't think of a good way to support this, so I don't intend to. > There will be one disk usage figure per package; users with several > filesystems are presumed to know what they're doing. I think I have the algorithm to do this. Please see if the following makes se

Re: Sizes and Packages in dselect

1995-10-03 Thread Ian Jackson
Erick Branderhorst writes ("Sizes and Packages in dselect"): > * diskspace requirements (displayed/registered) > [...] This is on the wishlist, and I think I know how to support it. > This will become more difficult when the different directory's where > parts of the packages are going to are mou