On Wed, 2008-08-20 at 16:09 -0400, Dave Jones wrote: > On Thu, Aug 21, 2008 at 12:43:18AM +0530, Rahul Sundaram wrote: > > seth vidal wrote: > > > A friend forwarded me this blog: > > > http://www.gdt.id.au/~gdt/blog/linux/autodeath.1024px > > > > > > and I wondered if it would be something to consider for fedora releases. > > > > > > This would NOT be as a default, but as a package you can install, if you > > > wish, to drop the route on your box after whatever expiration date. We > > > can set the release date in a file in the package and key from there. > > > > > > > > > If the package was included in a fedora repo we could have it have a > > > death date of whenever the release started + 14months (some wiggle room > > > for release slips) for example. > > > > > > Any thoughts? > > > > I think it is much better to hookup preupgrade with PackageKit so you > > get notification on your desktop > > Desktop machines typically aren't the problem in the 'setup once, and > left abandoned running out of date code past EOL' scenario. > I agree here. I wasn't as worried about desktops as servers/appliance-like machines. I put it down on my list to look at putting a simple cron job together in a package to do this. If anyone wants to do this before I do, please feel free, otherwise, I'll get to it when I can. thanks, -sv -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list