Dne 16.9.2014 v 17:36 Miloslav Trmač napsal(a):
----- Original Message -----
2. Ability to detect which processes depend on which versions of which
components.
We already managed to brought in systemd....
I can’t see how systemd helps. See the other discussions about Python/Ruby
modules that leave no obvious trace of their dependency after being loaded
into memory.
It has similar complexity and maybe packages could be described just like
services - so similar thing could be possibly reused here ?
Extra manual dependency information that would get obsolete?
Runtime removal of unused packages might be fun.
It could be something like 'fstrim' tool to run through cron...
3. Ability to automatically restart such processes without loosing state
(either completely transparently or with some user notification for
GUIs).
I'm not quite sure why we would need restart - simply delayed lazy release
of
unused packages would do the trick here - doing here state-full design is
much
more complex thing....
Because otherwise you end up with an old version of Firefox running for 60
days (or however long a laptop can run with suspends and no restarts; most
people about never quit their browser), and that version of Firefox
keeping an old version of a system-wide daemon running for 60 days as
well..
Sure if user is able to run Firefox for 60 days (though my usually goes out
of RAM in just a week or so, if it's not crashing earlier...) - then he is
happy user.
Until an exploit _that they have already installed an update for_ steals their data.
I guess something may show to user some nice gui dialog warning like - 'Hey
there is a new version installed - so 'restart' your browser to get new cool
feature' (FF normally already detects upgrades and suggest restart)
No, that’s not good enough. The OS should restart it for the user (other OSes already can do this). (In the case of user-invisible components there is no other option, and for user-visible GUIs it is also the right thing to do.)
As long as Firefox can't restart 'unnoticeable' while playing youtube video -
this is not an option - when admins updates machine - it just can't kill every
users' running firefox.
It's fine to place a warning somewhere and require restart with some 'many
hours' timeout - but for almost all "Firefox" updates - it's good enough to
restart it just sometimes latest - and for those 'have to restart' - it still
upon admins policy - not upon Fedora package maintainer....
Zdenek
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
