Ben Hutchings <b...@decadent.org.uk> writes:
> On Tue, 2012-06-19 at 15:29 +0300, Eugene V. Lyubimkin wrote:
>> Hello,
>>
>> On 2012-06-19 13:59, Tomas Pospisek wrote:
>> > This implies that an "apt-get install library" needs to trigger that
>> > restart.
>> > Which means that apt-get needs to depend on restart-services. So either
>> > restart-services and checkrestart should go into the apt package, or apt
>> > needs
>> > to depend on/recommend debian-goodies, which would currently pull in
>> > python,
>> > perl, curl, dialog and their respective dependencies.
>> >
>> > The later may be a technically working solution, but from a conceptual and
>> > a
>> > KISS point of view doesn't make sense to me.
>> >
>> > Is my conclusion correct so far?
>> >
>> > So if we want a "clean" solution, then checkrestart/restart-services would
>> > need
>> > to move into apt and get rid of the non-essential dependencies (get
>> > rewritten in
>> > shell or C).
>>
>> I believe this is a wrong layer for proposed functionality -- apt-get
>> (libapt) is not the only high-level package manager for Debian.
>>
>> If I were you, I'd look into dpkg file triggers instead. Triggers will
>> by the way automatically solve the problem that you don't restart
>> a service 5 times if 5 libraries were upgraded.
>
> But we still need one trigger per service? I don't think that's a good
> idea.
>
> Ben.
Do you? Why not a trigger that calls checkrestart?
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87vcilkosc.fsf@frosties.localnet
