Previously Anthony Towns wrote: > This makes it something of a pain if you're running low on disk space > and can't do an entire dist-upgrade in one go (ie, you can download > 1/3 of the .debs, install, download the next 1/3, install, and download > the last 1/3 and install, but only if you rm the downloaded .debs after > you're finished. I don't really see why you can't still do that? > Would it be possible to include, say, an archive of all packages > config.tar.gz's (which would presumably not be overly large) download > that, select the packages you want to install, and then download all > the .debs. No, since you should always be able to download a .deb and install that without any seperate files. And you can never get an archive of config-stuff up-to-date; see how Packages-files on mirrors are often out of synch for an example. > Should all packages just cope if dpkg doesn't support the config database, > or will some just cope, and others pre-depend, or fail their preinst, > or...? You can try coping, that is probably up to the package. For most packages that are non-interactive anyway it won't make much of a difference. > Is this avoidable? Will things become really ungainly if the package > has to be configured *before* being unpacked (or *anything* other than > the base system is unpacked)? This still leaves us with sed and mawk, > but drops out flex, bison, and stuff like that. I have yet to see a package needing flex or bison to configure itself.. > Should the preinst/postinst also check for these cases? In particular, it > seems like it might not be totally unreasonable to not entirely configure > a package (or perhaps not correctly), but still let it get installed, and > left as unconfigured. But what use is it to run the pre- & postinst if you didn't configure a pakage properly? That can result in a badly broken system. > Are there any example scripts available? No :) > I'm a little disinclined to trust a language that's never had a program > written in it; and in particular, it sounds like the confmodule has to > have a fair degree of intelligence about it. (am i interactive? then > ask these questions? oh, the user answered no? then skip these. ask > these too...) Always ask the questions, if it is non-interactive the frontend will simply not display them. Wichert. -- ============================================================================== This combination of bytes forms a message written to you by Wichert Akkerman. E-Mail: wakkerma@cs.leidenuniv.nl WWW: http://www.wi.leidenuniv.nl/~wichert/
Attachment:
pgp3faf7BYq8p.pgp
Description: PGP signature