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 mounted on seperate drive. Most > of the people will probably have a big drive where /usr is mounted on > and it will probably do, but with more and more packages coming up and > networking setups are being considered this might be worth a thought. 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. > * dselect creating it's list from several package files > > dselect is building it's selection list from a file (Packages or > something like that). What about making it possible that dselect > builds it selection list from different Packages files or optionally > >from all the Packages files it recursively finds from some root > directory. Perhaps this implemented now and I'm not aware. If so > please ignore this, otherwise please comment on this one. At this > moment a handy solution is probably catting all Packages files into > one. This is on the wishlist. Ian.
