Hi Björn Thanks for the suggestion. I'm not as a maintainer the one to decide whether cron-apt should be part of the standard installation or not. I'm not 100% sure who decides that actually.
I agree that it would be an useful feature, but I think such request will be rejected as the most important parts of the cron-apt functionality is actually included in apt (although disabled by default) since quite some time back, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512880 (this bug is about documenting the additional value of cron-apt compared to the functionality in apt itself). I would not argue against having it part of the standard installation, but I'm not sure others would agree. The packages in the standard installation is quite limited. There are many other useful things that are not part of the standard install. Regarding linking in cron.daily it has been requested before but I do not want to do that by default as you may not want to load the network just because you start your computer. Many people start their computer and then want to check something quickly. In that case it would actually hurt more than it do good. Another point is that it does not help to have it in cron.daily now with modern computers where you just suspend it when you do not work with it. Also the function in apt itself is actually on cron.daily, see bug 512880 for more info. Best regards, // Ola On Wed, Jul 29, 2015 at 1:45 PM, Björn Siebke <bjoernsie...@web.de> wrote: > Package: cron-apt > Version: 0.9.2 > Severity: wishlist > > Dear Maintainer, > > I suggest this package to be included in the standard installation. From my > view, it is essential for keeping a system secure to have all packages > updated > regularly by default. > > Moreover the standard configuration should be that /usr/sbin/cron-apt is > linked > by /etc/cron.daily/cron-apt so that the script runs on startup not only > during > the night as the current configuration. > > As long as no package is updated by default I don't see any risk, but only > big > advantages. > > I think it is especially important to include cron-apt in the standard > installation because I thought myself safe falsely after installation: > Supposedly due to a fresh "apt-get update" during install process one of > the > first things a fresh Debian installation does is display a "new updates" > notification. So the user - in this case me - thinks that this is a > preconfigured feature and that there is nothing more to do. It took me > months > to discover by accident that this is not true. > > I am open for any discussion! Thanks! > Björn > > > > -- System Information: > Debian Release: 8.1 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) > Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages cron-apt depends on: > ii apt 1.0.9.8 > > Versions of packages cron-apt recommends: > ii bsd-mailx [mailx] 8.1.2-0.20141216cvs-2 > ii cron 3.0pl1-127 > ii liblockfile1 1.09-6 > > cron-apt suggests no packages. > > -- no debconf information > -- --- Inguza Technology AB --- MSc in Information Technology ---- / o...@inguza.com Annebergsslingan 37 \ | o...@debian.org 654 65 KARLSTAD | | http://inguza.com/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / ---------------------------------------------------------------
