Thanks Bob for the clarification of the situation. Best regards,
// Ola On Sun, Aug 19, 2007 at 12:16:42PM -0600, Bob Proulx wrote: > Martin J. Carter wrote: > > Please update the manual page for cron-apt, to reflect the change from > > apt-get to aptitude in etch. > > In general for Etch aptitude is now the recommended APT frontend tool > while apt-get is still fully supported. But aptitude is still young > and not as mature as apt-get. For some applications such as cron-apt > the apt-get frontend is still a better default fit than the aptitude > frontend. > > There has been no change from apt-get to aptitude in Etch for > cron-apt. Since cron-apt uses apt-get by default (which is allowed as > apt-get is still fully supported in Etch) the documentation is correct > at this time for cron-apt. No change should be made. > > Use of apt-get here does not create any issues when used in the > default configuration since the default simply downloads packages and > notifies the user so that they are available and ready for manual > installation. > > If the admin chooses to configure cron-apt to automatically install > from a depot (e.g. 'apt-get install -y') then there is still no > conflict with aptitude. One of the features of aptitude is marking > packages as either manually installed or installed as a dependency. > In this case any packages would have been previously installed and the > previous status configuration would have applied. There would be no > changes and no issues with mixing apt-get and aptitude. The package > name list before is the same as the package name list after, only the > versions have changed, and aptitude's installation information is > unchanged. > > Bob > > -- --------------------- Ola Lundqvist --------------------------- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://opalsys.net/ +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
